Generate kind-correct wildcards when selecting from a wildcard #17025
Conversation
This file contains 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
Previously, derivedSelect would incorrectly approximate `fn.R` by `? >: Nothing <: Any` in `i16997.min.scala`, which subsequently lead to a kind-incorrect type application `Any[Y]` that broke type inference. scala#16999 proposed to fix this by changing type inference, but it seems like we don't need to do that if we make sure our wildcards are always kind-correct. Note that the wildcard logic in lookupRefined could be removed: it seems like it was supposed to be used by `reduceProjection` according to its documentation, but the constructor of `NamedType` disallows wildcards as prefixes so it didn't actually do anything there. Co-Authored-By: Dale Wijnand <dale.wijnand@gmail.com>
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.
Previously, derivedSelect would incorrectly approximate
fn.Rby? >: Nothing <: Anyini16997.min.scala, which subsequently lead to a kind-incorrect type applicationAny[Y]that broke type inference. #16999 proposed to fix this by changing type inference, but it seems like we don't need to do that if we make sure our wildcards are always kind-correct.Note that the wildcard logic in lookupRefined could be removed: it seems like it was supposed to be used by
reduceProjectionaccording to its documentation, but the constructor ofNamedTypedisallows wildcards as prefixes so it didn't actually do anything there.Co-Authored-By: Dale Wijnand dale.wijnand@gmail.com