Add operator precedence test #78
Open
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
mhanberg
pushed a commit
that referenced
this pull request
Jan 22, 2026
Fixes one of the errors found by #78 `Spitfire.parse("a..b..c//d")` is producing `a..(b..c//d)` instead of `(a..(b..c))//d`. This is due to the wrong precedence being used for `@range_op`, and the parsing of nested ranges causing the inner range to consume the `//` operator.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds a set of tests that iterative through different combinations of elixir expressions (matched, unmatched, no parens) joined by unary, binary and ternary operators. It validates if the parser correctly builds AST nodes, preserves precedence rules, operator binding power and associativity. It also exercises the parser on do blocks and no parens expressions.