You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a reason why total_in(&self) / total_out(&self) isn't implemented for Gzip decoders/encoders? It is present for both Zlib and Deflate and could be really useful for monitoring progress of the operation.
Looking at the decoder implementations, they seem to be using the same DeflateDecoder underneath - only wrapped in CrcReader<>. So it could be as simple as forwarding the function call in.
It could be also nice to separate these functions into a trait to provide a generic interface for libraries building on top of flate2.
The text was updated successfully, but these errors were encountered:
Even though I don't have an answer, I wonder if that could be an oversight that could be remedied by adding these methods and wiring them up? Could that work as 'as simple as possible' solution? And possible, do we have tests that could be extended to use that new functionality?
Hello
Is there a reason why
total_in(&self)
/total_out(&self)
isn't implemented for Gzip decoders/encoders? It is present for both Zlib and Deflate and could be really useful for monitoring progress of the operation.Looking at the decoder implementations, they seem to be using the same
DeflateDecoder
underneath - only wrapped inCrcReader<>
. So it could be as simple as forwarding the function call in.It could be also nice to separate these functions into a trait to provide a generic interface for libraries building on top of flate2.
The text was updated successfully, but these errors were encountered: