Open
Conversation
adsharma
commented
Jan 24, 2025
| OP, | ||
| STRING, | ||
| NEWLINE, | ||
| DEDENT, |
Author
There was a problem hiding this comment.
I would like the tokenizer to output DEDENT + NEWLINE here.
That would allow the parser I'm working on to parse
pmatch-statement NEWLINE return-statement
as two statements separated by a newline. The current tokenizer behavior makes it awkward to parse.
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.
Add a test case to document and discuss a change in tokenizer behavior around DEDENT + NEWLINE
Related to: #107