Skip to content

Don't generate illegal types when clarifying implicit errors #14068

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
Dec 13, 2021
Merged

Don't generate illegal types when clarifying implicit errors #14068

merged 1 commit into from
Dec 13, 2021

Conversation

@odersky
Copy link
Contributor

@odersky odersky commented Dec 7, 2021

Fixes #13987

@odersky odersky requested a review from abgruszecki December 11, 2021 15:03
abgruszecki
abgruszecki approved these changes Dec 13, 2021
View reviewed changes
Copy link
Contributor

@abgruszecki abgruszecki left a comment

Choose a reason for hiding this comment

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

LGTM.

@abgruszecki abgruszecki merged commit 472c8ff into scala:master Dec 13, 2021
@abgruszecki abgruszecki deleted the fix-13987 branch December 13, 2021 15:36
@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

Reviewers

1 more reviewer

@abgruszecki abgruszecki abgruszecki approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@abgruszecki abgruszecki

Labels

None yet

Projects

None yet

Milestone

3.1.2

Development

Successfully merging this pull request may close these issues.

assertion failed: <: X[?] & Xa[?] when searching for a higher-kinded type variable with an intersection

3 participants

@odersky @abgruszecki @Kordyjan