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

Indicate name of classfile where leaky mapping of existential type happens #13879

Merged
merged 1 commit into from
Nov 4, 2021

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Nov 4, 2021

Fixes #13873

@odersky
Copy link
Contributor Author

odersky commented Nov 4, 2021

Do we have a test setup that mixes Scala 2 and Scala 3 compilation? If that's the case I can push the test files that show that the problem is fixed. But it's pretty obvious from the code alone as well.

@nicolasstucki nicolasstucki changed the title Indicate name of classfile where leaky mapping of existential type ha… Indicate name of classfile where leaky mapping of existential type happens Nov 4, 2021
@nicolasstucki
Copy link
Contributor

Do we have a test setup that mixes Scala 2 and Scala 3 compilation?

As far as I know, we do not have any infrastructure for that.

@odersky odersky merged commit 483bf2c into scala:master Nov 4, 2021
@odersky odersky deleted the fix-13873 branch November 4, 2021 11:41
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.

unhelpful warning for unsupported Scala 2 existential types
2 participants