fix: limit TypePattern's VariableDeclaratorList to a single VariableDeclarator #734
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.
What changed with this PR:
There exists some ambiguity in the parser within comma-separated
TypePatterns, becauseTypePatterncontains aVariableDeclaratorList, which is comma-separatedVariableDeclarators. The parser cannot currently determine where theVariableDeclaratorListends and the nextTypePatternbegins. This was previously realized in #707, withinComponentPatternList, and is now experienced in #733, withinSwitchLabel.I realized that the JLS specifically mentions semantic restrictions that make it easy to resolve this ambiguity. From 14.30.1. Kinds of Patterns (emphasis mine):
As such, this PR limits
TypePattern'sVariableDeclaratorListto a singleVariableDeclaratorin our parser. That change also allowed me to remove the patch that was added in #708, as this fix also resolves the ambiguity for the issue seen in #707.Example
Input
Output
Relative issues or prs:
Closes #733