Add move-to-front transform#14743
Open
fze-fze wants to merge 1 commit into
Open
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
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.
Describe your change:
Add a pure Python implementation of the move-to-front transform in
data_compression/move_to_front.py.The new module includes:
move_to_front_encode()to encode text as move-to-front indexesmove_to_front_decode()to reconstruct text from encoded indexesThis fits naturally beside
data_compression/burrows_wheeler.py, whose module documentation already mentions move-to-front transform as a common follow-up compression step.Checklist:
Local verification
I also ran a round-trip smoke test for several strings against a printable ASCII alphabet.