Prevent deprecation of _ in type patterns
#18847
Closed
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
sjrd
reviewed
Nov 5, 2023
| // under -source:future, `_` is deprecated for wildcard arguments of types: use `?` instead | ||
| val xs: List[_] = Nil |
There was a problem hiding this comment.
This change does not seem right. In that position, List[_] is not a pattern type, so _ should stay deprecated.
There was a problem hiding this comment.
Thanks very much, I've removed the change to the test now. The fix isn't as trivial as I thought it was.
There was a problem hiding this comment.
Currently this warining is not properly tested for cases that are not in patterns. I am adding tests in #18813.
|
Closed since already fixed in #18887 |
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.
An attempt to prevent the deprecation of
_in type patterns as discussed in #18808