Skip to content
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

Harden erasure of PolyFunction apply's #14075

Merged
merged 2 commits into from Jan 4, 2022
Merged

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Dec 8, 2021

Fix in case qualifier is an intersection with a PolyFunction type.

Fixes #13950

Fix in case qualifier is an intersection with a PolyFunction type.

Fixes scala#13950
@odersky
Copy link
Contributor Author

odersky commented Jan 3, 2022

@smarter ping for review

@smarter
Copy link
Member

smarter commented Jan 3, 2022

Oops yeah I wanted to see if I could avoid the AndType special-casing, I'll take care of it tomorrow.

The previous approach did not handle situations where the qualifier was
not directly an AndType, but a type whose underlying type is an
AndType like in example2 and example3 (this commit also minimizes the original
example further).
@smarter smarter assigned odersky and unassigned smarter Jan 4, 2022
@odersky
Copy link
Contributor Author

odersky commented Jan 4, 2022

@smarter I think I also prefer this solution.

@odersky odersky merged commit ab125eb into scala:master Jan 4, 2022
@odersky odersky deleted the fix-13950 branch January 4, 2022 21:09
@Kordyjan Kordyjan added this to the 3.1.2 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.

Crash when typing applied polyfunction after match
3 participants