Milosz Krajewski

Please note that having non-contiguous blocks of any size will not guarantee "At any point of time last 64k of uncompressed data needs to be accessible at fixed address in...

If have a feeling that by saying "I want to be able to effectively stream compression/decompression, but without using the Stream class" @AArnott meant using ReadOnlySequence and IBufferWriter for **streaming**...

I was looking at this today. Making compression / decompression to/from IBufferWriter and ReadOnlySequence would require duplication the whole Streaming logic or creating some streaming abstraction and having two implementations...

I am working on generic approach, which is taking some time. 1. Generic, so it won't need separate implementation for other stream-like objects (and anything remotely looking like `.GimmeNextBytes(N)` and...

> @MiloszKrajewski An API that fits your two methods is `PipeReader`. If the LZ4 algorithm could operate based on that (and `PipeWriter` it would be able to interop with many...

I think a lot of it is addressed in [1.3.0-beta](https://github.com/MiloszKrajewski/K4os.Compression.LZ4/releases/tag/1.3.0-beta). I know you did a lot of good work in #74 but you caught in the middle of a very...

That's exactly what I'm working on right now (see branch `abstracted-streams`). I'm trying to abstract stream into something lighten (let's call it ByteProducer / ByteConsumer), so stream would also be...

@mirasrael NOTE, `LZ4Pickler` is much lighter protocol (support for `Span`, and `IBufferWriter`, very low GC use, uses `stackalloc` below 1024 bytes, etc). It is NOT LZ4 Frame compatible though (it...

Yup, ` where TBufferWriter : struct, IBufferWriter` makes sense to wrap some pooled dynamic byte array. I will definitely add it to next release.

Lot of new functionality around streams, ReadOnlySpans, Memory and BufferWriters in [1.3.0-beta](https://github.com/MiloszKrajewski/K4os.Compression.LZ4/releases/tag/1.3.0-beta)