Start included-range roots at the selected byte - #973
Merged
Conversation
- Re-seek or preserve overlapping tokens at range boundaries. - Align initial parser stack offset with the first included byte. - Route empty-stack end points through a new accessor method. - Add parity checks for root start bytes and start points. - Update docs to record the root-start fix as partial parity. Buckley-Change-Hash: sha256:57418d5725d1b68369e0708b92c5ab1222839c12865933a4812ea5f978a0b0da Buckley-Change-Stats: files=8 insertions=311 deletions=37 binaries=0
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.
Summary
Why
The Go included-range root began at byte zero. The C root began at byte 26. This change moves root-start ownership into the producer.
Tests
All Docker runs used one grammar and one CPU. They exited zero without timeout or memory failure.
Remaining work
Go has 10 root children, while C has seven. Compact and forest included-range routes remain uncertified. Keep
dispatch.go.source-file-rootlive.This PR does not claim full parity or campaign closure.