Parser: Allow inline in expressions outside of case statements#1821
Merged
marcoroth merged 3 commits intoJun 28, 2026
Merged
Conversation
in expressions outside of case statements
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
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.
Currently using
value in patternwithout an accompanied case statement raisesERBControlFlowScopeError.Now a pattern match predicate only increments in_node_count when it's accompanied by a case statement.
I used Claude to help me understand how to make this change -- so please look it over and determine if this is the correct type of fix.
Fixes #1758