ScalametaParser: constrain match type pattern #2886
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
tgodzik
requested changes
Sep 26, 2022
tests/shared/src/test/scala/scala/meta/tests/parsers/dotty/MatchTypeSuite.scala
Show resolved
Hide resolved
tests/shared/src/test/scala/scala/meta/tests/parsers/dotty/MatchTypeSuite.scala
Show resolved
Hide resolved
tgodzik
approved these changes
Sep 26, 2022
Currently, unlike pattern matching for Terms which follows a different parsing logic and produces Pat trees, pattern matching for Types uses exactly the same logic as regular Types. This occasionally leads to incorrect parsing, and here we try to address the specific problem of parsing a wildcards and anonymous params which is different in a type pattern match context.
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, unlike pattern matching for Terms which follows a different parsing logic and produces Pat trees, pattern matching for Types uses exactly the same logic as regular Types.
This occasionally leads to incorrect parsing, and here we try to address the specific problem of parsing a wildcards and anonymous params which is different in a type pattern match context.
Helps with #2807.