4:30:28Bikere: speeding up read-byte, i wonder how plausible it would be to have the compiler put in an unboxed read-byte when possible... probably would be difficult because streams are pretty dynamic, but might be interesting to try
4:31:34Bikefirst off i'll make the generic version less crappy, though
14:08:53Bikeok, first stream bug detected: you're allowed to open a stream with an element type like (unsigned-byte 37), and if you write to that clasp crashes
14:10:26Bikehm, are we allowed to upgrade stream element types...
14:24:49Bikedrmeister: would there be any problem with only supporting binary stream element types of, say, ([un]signed-byte n) for n = 8,16,32,64
14:29:37Bikehmm. sbcl seems to support arbitrarily sized bytes
14:29:44Bikethough it interprets unsigned-byte itself as (unsigned-byte 8)
14:32:27Bike"FIXME: let's do it the hard way, then (but ignore things like endianness, efficiency, and the necessary doupling between these and the output routines)." okay, maybe it's not supported very well