use zlib_rs api
#513
Draft
use zlib_rs api
#513
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
folkertdev
force-pushed
the
zlib-rs-api
branch
from
867ada4 to
46ea2c4
Compare
folkertdev
force-pushed
the
zlib-rs-api
branch
from
46ea2c4 to
32a775b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an initial design for using the
zlib_rsAPI, calling the safe functions that it exposes rather than the unsafe wrappers oflibz-rs-sys.I'm designing the flate2 side here, the actual implementation still uses
libz-rs-sysbecausezlib-rsdoes not export some things that we need here.Inspired by GitoxideLabs/gitoxide#2155.