Add portable bzip2 format scanning primitives - #1
Merged
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
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.
Replace the scaffold API with the first correctness-bearing bzip2 layer: a bounded MSB-first bit reader, bzip2 CRC primitives, and a portable rolling-window scanner covering all eight marker alignments.
Expose the scanner through Rust and Python APIs, with differential tests against libbz2 for single-block, multi-block, and concatenated streams. Scanner results remain explicitly unvalidated candidates pending full decoding and CRC-chain validation.
See “Architecture” in DEV.md and the implementation-status section in README.md for design boundaries and next layers.