Properly erase Java intersections #8946
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smarter
force-pushed
the
java-intersection-erasure
branch
from
6e7debe to
de9669e
Compare
Java intersections erase to their first member which is always a class type. To enforce this we need to: - Make sure we don't use `&` when creating these intersections - Make sure `simplified` does not simplify intersections which appear in method types.
smarter
changed the title
smarter
force-pushed
the
java-intersection-erasure
branch
from
de9669e to
a543e00
Compare
|
Ping for review. |
odersky
approved these changes
May 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Java intersections erase to their first member which is always a class
type. To enforce this we need to:
&when creating these intersectionssimplifieddoes not simplify intersectionswhich appear in method types.