Fix bugs in ambiguity management #30
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
maxbrunsfeld
pushed a commit
that referenced
this pull request
Feb 24, 2016
Fix bugs in ambiguity management
|
🤘 that’s pretty fantastic work dude! |
BekaValentine
pushed a commit
that referenced
this pull request
Feb 23, 2021
Restructure some rules to allow typescript to extend this grammar
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.
Fixes an issue discovered in tree-sitter/tree-sitter-ruby#16
Debugging
This adds a
ts_document_print_debugging_graphsfunction. When this boolean flag is set on the document, it dumps a DOT representation of the graph-structured parse stack after every parse action. This output can be piped directly todotto produce a sequence of graphs and parse actions, like this:
#### Bug fixThis fixes a bug wherein ambiguities were merged incorrectly, producing nonsensical parse trees.