Skip to content

Fix isMatch #12206

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

Merged
merged 3 commits into from
Apr 29, 2021
Merged

Fix isMatch #12206

merged 3 commits into from
Apr 29, 2021

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Apr 23, 2021

An applied type that is an alias of an applied match type is an applied match type itself.
Previously that was not the case, which led to typed that could logically be reduced but were
not.

Fixes #12194

There, the case was that we had a Tuple.Union type that was an alias of a Tuple.Fold type instance, which was an alias
of a match type. The Tuple.Union did did not get reduced since it was not regarded as a match type alias itself.

odersky added 2 commits April 24, 2021 10:55
Avoid steps can yield match types that should be normalized to keep things clean. This means
avoidance does the same steps as simplification in this respect.

Fixes scala#12194
An applied type that is an alias of an applied match type is an applied match type itself.
Previously that was not the case, which led to typed that could logically be reduced but were
not.
@odersky odersky changed the title Normalize after avoidance Fix isMatch Apr 24, 2021
@odersky odersky merged commit 311dc17 into scala:master Apr 29, 2021
@odersky odersky deleted the fix-i12194 branch April 29, 2021 19:25
@Kordyjan Kordyjan added this to the 3.0.1 milestone Aug 2, 2023
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 this pull request may close these issues.

Exception while typing [extremely long type here]
3 participants