A question came up recently about using cbor/decode to lazily parse an input stream, where data from the underlying stream was getting lost.
This is due to the fact that internally, decode will automatically coerce its argument into a java.io.DataInputStream by first calling clojure.java.io/input-stream on it. The implementation of input-stream always wraps a java.io.BufferedInputStream around the result, which in turn means that the first read on a bare InputStream sucks more data than expected into the internal buffer, which is then discarded!
The immediate solution is to make sure you're always passing a DataInputStream to the decode methods, but a better approach would be to not try coercing things that are already InputStreams and to clearly document this behavior on the functions.
A question came up recently about using
cbor/decodeto lazily parse an input stream, where data from the underlying stream was getting lost.This is due to the fact that internally,
decodewill automatically coerce its argument into ajava.io.DataInputStreamby first callingclojure.java.io/input-streamon it. The implementation ofinput-streamalways wraps ajava.io.BufferedInputStreamaround the result, which in turn means that the first read on a bareInputStreamsucks more data than expected into the internal buffer, which is then discarded!The immediate solution is to make sure you're always passing a
DataInputStreamto thedecodemethods, but a better approach would be to not try coercing things that are alreadyInputStreams and to clearly document this behavior on the functions.