lexer: do not lex decimal numbers when the parser won't accept them #655
Conversation
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
A conflict arises with code positioning and decimal numbers (e.g., 2.2). To address this, the incremental API of Menhir is now employed. When the lexer identifies a decimal number, but the parser is in a state where a decimal number isn't accepted, it returns the a number-dot-number token sequence instead.
mbbarbosa
approved these changes
Oct 29, 2024
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.
A conflict arises with code positioning and decimal numbers (e.g., 2.2). To address this, the incremental API of Menhir is now employed. When the lexer identifies a decimal number, but the parser is in a state where a decimal number isn't accepted, it returns the a number-dot-number token sequence instead.