README: move integer automaton into How it works, explain the encoding#33
Merged
Conversation
…oding The automaton is only meaningful once the reader knows how integers are encoded, so it now sits in the How it works section rather than the quick start. Added the encoding: sign-magnitude, least-significant bit first, with a leading sign bit and * padding, so the diagram can actually be traced. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The integer automaton is only meaningful once the reader knows how integers are encoded, so it moves out of the quick start and into the How it works section, right where the encoding can be explained.
Added: the arithmetic encoding is sign-magnitude, least-significant bit first — a leading sign bit (
0non-negative,1negative), then the magnitude bits low-to-high, with*padding multi-tape arguments. With that in hand the diagram can actually be traced (start state reads the sign; the rest scan the magnitude bits).🤖 Generated with Claude Code