Add bzip3 and LZ4 support #98
Merged
+68
−1
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
bzip3 is a better, faster and stronger spiritual successor to bzip2. This is available in the official repositories of many systems:
LZ4 is a lossless compression algorithm that is focused on compression and decompression speed. This is used in many system software. This is available in the official repositories of many systems:
archive::is_lz4does not support legacy formats (support v1.4+ only). This is similar toarchive::is_zst. The magic number was changed almost 10 years ago, so it doesn't matter for practical purposes.I don't know how to generate skippable frames, so I haven't tested it. However, skippable frames in Zstandard are compatible with skippable frames in LZ4.1 Since
archive::is_lz4is based onarchive::is_zst, so this should work fine.Resources
Footnotes
https://datatracker.ietf.org/doc/html/rfc8878#section-3.1.2 ↩