Fix semicolon line attribution #178
Merged
Conversation
This file contains 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
For some reason, we were continuing to look for more whitespace tokens after consuming an explicit semicolon. This is unnecessary since the scanner can just come back for the remaining whitespace, if any exists. It also leads to incorrect attribution of the location of the semicolon, so it's better to just break at the semicolon. Fixes #177 -- with this change, the test file in that issue gets parsed as: ``` (source_file [0, 0] - [2, 0] (simple_identifier [0, 0] - [0, 3]) (_semi [0, 3] - [0, 4]) (simple_identifier [1, 0] - [1, 3]) (_semi [1, 3] - [1, 4])) ```
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.
For some reason, we were continuing to look for more whitespace tokens after consuming an explicit semicolon. This is unnecessary since the scanner can just come back for the remaining whitespace, if any exists. It also leads to incorrect attribution of the location of the semicolon, so it's better to just break at the semicolon.
Fixes #177 -- with this change, the test file in that issue gets parsed as: