[POC] feat: Allow the parser to direct the which tokens it expects from the lexer #673
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
This was referenced Jul 5, 2022
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.
AKA lexer modes.
Quick-ish experiment to investigate if it is feasible to use lalrpop for https://github.com/influxdata/flux . Seems to work for the purpose of allowing division (
/) and regex/a.+/to co-exist in a grammar. The code is in a hacky state right now though due to the neecessary addition ofLexerIteratorso there would need to be more work before this could be merged. I also don't know how well this scales to other grammars. Implementation is based on a cursory understanding of the paper mentioned here #195 (comment) .Closes #195