-
-
Notifications
You must be signed in to change notification settings - Fork 4k
add native zstd support #19793
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add native zstd support #19793
Conversation
Should this have a small migration guide entry to state that an additional feature is required when using |
its a default feature, so unless you're using default-features=false there's no migration |
b48013b
to
7c2fb6d
Compare
@atlv24 doing |
it's mentioned in the migration guide 👍 |
Oh thanks, then I'm happy :D |
# Objective - add support for alternate zstd backend through `zstd` for faster decompression ## Solution - make existing `zstd` feature only specify that support is required, disambiguate which backend to use via two other features `zstd_native` and `zstd_rust`. - Similar to the approach taken by #18411, but we keep current behavior by defaulting to the rust implementation because its safer, and isolate this change. NOTE: the default feature-set may seem to not currently require `zstd`, but it does, it is enabled transitively by the `tonemapping_luts` feature, which is a default feature. Thus this does not add default features. ## Testing - Cargo clippy on both feature combinations
Objective
zstd
for faster decompressionSolution
zstd
feature only specify that support is required, disambiguate which backend to use via two other featureszstd_native
andzstd_rust
.NOTE: the default feature-set may seem to not currently require
zstd
, but it does, it is enabled transitively by thetonemapping_luts
feature, which is a default feature. Thus this does not add default features.Testing