Merged
Conversation
Co-authored-by: Jason Zaugg <[email protected]>
Member
|
Looks good 👍 |
lrytz
approved these changes
Jun 16, 2025
Contributor
Is this expect warning? |
Contributor
Member
|
I'm adding this to the 2.13.17 release notes. @som-snytt you might attempt to improve the PR title and description, since it seems people are landing here. |
Contributor
Author
|
@SethTisue thanks, I made it into the release notes! for all the wrong reasons. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
-Xlint:infer-anywarns if a type parameter is inferred asAny. With this commit, it warns if a higher-kinded type parameter is inferred to beAnyorNothing, which is also permitted but may be unexpected.As usual, the lint can be selectively turned off:
-Xlint:_,-infer-anyor silenced:or locally in source
Motivating examples in the tests or the ticket, or the previous PR and its ticket. Note that Scala 3 doesn't have the same limitations for typechecking. The lint warns about a limitation in Scala 2.
See scala/bug#13128 for follow-up discussion.
Fixes scala/bug#12044
via #4401 which after ten years is ready to be uncorked.