-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Compare types as capture sets in mergeRefinedOrApplied #23045
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
Open
DolphinChips
wants to merge
1
commit into
scala:main
Choose a base branch
from
DolphinChips:i23032
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
def f[F[_], T]: F[Unit] | F[T] = ??? | ||
def x[F[_]] = f.toString |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
=:=
usesTypeComparer
to check two types are equivalent (subtypes of each other), which is expensive and we need to be careful when using it.The reason we have one
TypeParamRef
and oneTypeVar
is because we choose to widentp1
inapproximateOr
.I would like to try the following:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your suggested change works. I also decided to experiment with other solutions and found out that either adding the following case:
or applying the following patch
also fix the issue. So my questions are:
case tp1: TypeVar
branch?.stripTypeVar
also a valid solution?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
case tp1: TypeVar
can be hit iftp1
isTypeVar
andtp2
isTypeParamRef
, although it may not happen here because the left branch of a union type is widened first inapproximateOr
if both sides widening succeed (see2.6
). Since the ordering is arbitary, I think it's better to cover all possibilities in case the algorithm is changed.TypeParamRef
andTypeVar
) beforestripTypeVar
, to avoid covering unintended types.