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
Remove deprecated advice #10641
base: 2.13.x
Are you sure you want to change the base?
Remove deprecated advice #10641
Conversation
Is there a different recommendation we could substitute? |
Every warning is nowarnable. Unfortunately, Scala 3 has different syntax and categories and messages, so there is no specific advice that cross-compiles. |
What is the recommended mitigation in Scala 3? I'm asking for a couple reasons, one is that I'd like the PR description to document the current situation for users, the other is that maybe we could do something on the Scala 3 side. |
and
TIL dotty doesn't warn nonunit-statement for value discard. (The conversion moves a result expression to statement position, even the user did not "write it like that".) |
Would be good if we could limit it to one warning. |
Well, that may be true now. IIRC they used to have slightly different triggers.
|
I don't mean to be difficult, but I don't feel comfortable merging this unless we can, at the same time, provide users extremely clear guidance about how to proceed, including in cross-built projects. Changing the behavior without providing that seems like churn to me. |
@SethTisue they will have to supply version-specific This PR doesn't change behavior, only the "advice". |
Scala 3 won't mitigate warning value discard under
expr: Unit
syntax, so don't advertise it.The mitigation is not removed, for convenience, and because no one writes normal code like that.
To see how to suppress warnings, use
-Wconf:any:warning-verbose
in Scala 2 and-Wconf:any:verbose
in Scala 3.Extracted from stalled #10476