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

Constrain pattern types when typing a match type case #14563

Merged
merged 1 commit into from Feb 28, 2022

Conversation

dwijnand
Copy link
Member

This was missing, compared to typedType, and was causing constraints to
be missing, leading to legal code not compiling.

This was missing, compared to typedType, and was causing constraints to
be missing, leading to legal code not compiling.
@dwijnand dwijnand marked this pull request as ready for review February 25, 2022 18:18
@odersky odersky requested review from abgruszecki and OlivierBlanvillain and removed request for odersky February 25, 2022 18:53
@odersky
Copy link
Contributor

odersky commented Feb 25, 2022

I believe Olivier and/or Alex should take a look at it. I am not an expert here.

@dwijnand dwijnand merged commit d57a4a4 into scala:main Feb 28, 2022
@dwijnand dwijnand deleted the match-types-bounds/i14151-again branch February 28, 2022 16:01
@Kordyjan Kordyjan added this to the 3.1.3 milestone Aug 1, 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.

Match type on parameterized trait doesn't preserve input parameter in type variable
5 participants