Open martinraison opened 9 years ago
Currently byte-streams
doesn't handle nil
or empty sequences, mostly because I haven't thought through all the implications of (for instance) implicitly transforming nil
into an empty byte-array. I agree, though, that it puts an unfortunate burden on you. Leaving this issue open until I have a better answer.
:+1:
Is this by design? I would expect to get an empty byte array instead.
Since
(bs/to-byte-array [(byte-array [2 3 4]) (byte-array [5 6])])
works, the behavior seems surprising to me. It requires checking that the array is not empty before callingto-byte-array
.