gh-153569: drive tokenizer input through source offsets - #156482
Draft
pablogsal wants to merge 3 commits into
Draft
gh-153569: drive tokenizer input through source offsets#156482pablogsal wants to merge 3 commits into
pablogsal wants to merge 3 commits into
Conversation
Member
Author
|
Do not review until #156472 lands. |
pablogsal
force-pushed
the
gh-153569-tokenizer-offset-state
branch
from
August 28, 2026 15:32
dddc133 to
1753605
Compare
Member
Author
|
#156472 has landed; this is rebased on it now. |
pablogsal
force-pushed
the
gh-153569-tokenizer-offset-state
branch
from
August 28, 2026 16:24
1753605 to
8bd1d3a
Compare
pablogsal
changed the title
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 common reader now keeps decoded file,
readline(), and interactive input inSourceText, and prepared input walks the same retained source with a cursor.The lexer still gets its current pointer view for now. When the retained source grows, those live pointers are saved as offsets and restored after relocation, so later PRs can move the scanners without another input implementation.
This follows #156472 and is the first split from #153569.