Skip to content

Fix existing GADT constraints with introduced pattern-bound symbols #22928

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Apr 9, 2025
Merged

Fix existing GADT constraints with introduced pattern-bound symbols #22928

merged 1 commit into from
Apr 9, 2025

Conversation

dwijnand
Copy link
Member

@dwijnand dwijnand commented Apr 7, 2025

Fixes #22879

@dwijnand dwijnand marked this pull request as ready for review April 8, 2025 07:00
@dwijnand dwijnand requested a review from odersky April 8, 2025 07:03
odersky
odersky approved these changes Apr 8, 2025
View reviewed changes
Copy link
Contributor

@odersky odersky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@Gedochao
Copy link
Contributor

Gedochao commented Apr 9, 2025

@dwijnand @odersky should we merge this?

@odersky odersky merged commit dcf176b into scala:main Apr 9, 2025
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@odersky odersky odersky approved these changes

Assignees

@odersky odersky

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Type mismatch error using case class extractor with multiple type parameters and constraints
3 participants
@dwijnand @Gedochao @odersky