Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Precedence works in mysterious ways #31

Closed
maxbrunsfeld opened this issue Feb 24, 2016 · 0 comments · Fixed by #49
Closed

Precedence works in mysterious ways #31

maxbrunsfeld opened this issue Feb 24, 2016 · 0 comments · Fixed by #49

Comments

@maxbrunsfeld
Copy link
Contributor

Refs tree-sitter/tree-sitter-ruby#16 (comment)

  1. The static conflict resolution algorithm could use some refinement. The code that checks for expected conflicts and displays the unexpected conflicts to the user actually does a better job of analyzing the conflict than the resolution algorithm.
  2. Currently, since precedence only affects how tightly adjacent elements of a sequence bind to each other, precedence has no effect on singleton production like: lhs: $ => $.variable. I explicitly made it this way, but it turns out to be dumb.
BekaValentine pushed a commit that referenced this issue Feb 23, 2021
Fix some issues I found when parsing React.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant