Decode from iterator

[marshallpierce]

Decode from iterator

[kanekv]

golang follows this pattern everywhere, e.g.: https://golang.org/pkg/encoding/base64/#NewDecoder

[marshallpierce]

That would be convenient, for sure, but I don't see a clear path to make it fast. A big part of the reason the crate is fast is that it can decode and encode from slices.

[partim]

A compromise would be to allow decoding a sequence of slices. It would just have to keep some state from the potentially incomplete end of a slice between iterations.

[marshallpierce]

That sounds like the decode-side equivalent of the existing EncoderWriter. Shouldn't be too hard to adapt an iterator to a Read, I would imagine...

[partim]

Perhaps a DecoderWriter would be more convenient? I.e., a writer that is fed encoded data and writes decoded data to the underlying writer. That works neatly atop a vec.

[AlexTMjugador]

My two cents here: with a crate like iter_read you can easily turn an iterator over bytes to a Read that can then be used with the DecoderReader struct of this crate. This doesn't involve collecting the entire input data to a temporary buffer again.

[marshallpierce]

That sounds like a good solution. (The DecoderReader will buffer chunks internally, so there's still some buffering.)