Guillaume E

I assume this issue is the same feature request as #72?

> What's your take on it? Is `alloc` the only way to move forward without a complete redesign? Apologies for the delay in replying. It may be worth redesigning the...

This is currently not supported, but would be a good enhancement.

Could you document how standard this "Broadcom modification" is? I won't have much time to investigate this in the following weeks, but feel free to send a pull-request to support...

This is a very interesting point! I was wondering whether there was a generic way of transforming an `io::Write` into an `io::Read`. The opposite would be quite simple (read bytes...

I'm now wondering whether integrating with async/await would be the way to go to implement this. Something like taking [futures::io::AsyncRead](https://docs.rs/futures/0.3.5/futures/io/trait.AsyncRead.html) as input and writing to a [futures::io::AsyncWrite](https://docs.rs/futures/0.3.5/futures/io/trait.AsyncWrite.html) or a [futures::stream::Stream](https://docs.rs/futures/0.3.5/futures/stream/trait.Stream.html)...

I had a brief look, the [`min_const_generics` feature](https://github.com/rust-lang/rust/issues/74878) was indeed stabilized in 1.51, but we still need the more complex [`const_evaluatable_checked` feature](https://blog.rust-lang.org/2021/02/26/const-generics-mvp-beta.html#const-generics-with-complex-expressions) due to the `1

An LZMA stream can include an unpacked_size hint in its header (https://github.com/gendx/lzma-rs/blob/master/src/decode/lzma.rs#L61-L74), which the code then verifies to reject inconsistencies (https://github.com/gendx/lzma-rs/blob/master/src/decode/lzma.rs#L312-L320). Additionally, the LZMA2 format is a wrapper around LZMA,...

Would https://github.com/gendx/lzma-rs/pull/17 (or a variant of it) work for this use case?

Thanks @ibaryshnikov for your example. However, I don't see how it's not behaving as expected. You provide an expected unpacked size of 5048 bytes, but the decompressed output is only...