-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fix -Ytest-pickler with super trees #5516
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
Merged
Merged
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
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 |
---|---|---|
|
@@ -2,7 +2,6 @@ i94-nada.scala | |
i1812.scala | ||
i1867.scala | ||
i3067.scala | ||
t247.scala | ||
t2712-5.scala | ||
t284-pos.scala | ||
t3249 | ||
|
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.
I think neither old nor new version is right. What about this scenario?
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.
Yes, it's a bit weird, but if we change this then we need to change the pickling/unpickling scheme for super which currently does:
So won't work with mix being an AppliedType.
Alternatively we could change SuperType#underyling to work like SuperType#superType, currently they're different:
But note that in practice I haven't found a case where the current definition breaks something, e.g. in
findMember
we callunderlying
onSuperType
but that ends up working out sincefindMember
keeps around the prefix of the call aspre
which contains all the information we need to figure out the type parameters.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.
I believe
underlying
in supertype is fine.I don't see right now why pickler/unpickler has to change. Should we not instead change the TypeAssigner to do the same as
SuperType$superType
?Uh oh!
There was an error while loading. Please reload this page.
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.
Coming back to this PR 2 years (!) later, I believe I'm still confused by why
underlying
andsuperType
are different inSuperType
, if I follow your advice of makingTypeAssigner
use the same logic assuperType
to setsuperTpe
, then they would always be the same anyway. Would you mind taking another look at this?Uh oh!
There was an error while loading. Please reload this page.
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.
I don't have deep insights here either.
underlying
does not dobaseType
invocations, andsuperType
should probably do that.That said, I now think the change in TypeAssigner makes sense. If everything passes with that change, let's do it.