Warn by default on mismatch of presence/absence of an empty parameter list when overriding #8846
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
dwijnand
changed the title
dwijnand
changed the title
dwijnand
force-pushed
the
promote-override-nullary-to-2.13-and-Xsource-3
branch
3 times, most recently
from
c50606f
to
226273f
Compare
dwijnand
commented
Mar 31, 2020
This comment has been minimized.
This comment has been minimized.
|
|
|
Still faster than deprecating in 3.0 and removing in 3.1. 😄 |
dwijnand
force-pushed
the
promote-override-nullary-to-2.13-and-Xsource-3
branch
2 times, most recently
from
20aaee2
to
93c2664
Compare
lrytz
reviewed
Apr 3, 2020
lrytz
reviewed
Apr 3, 2020
dwijnand
force-pushed
the
promote-override-nullary-to-2.13-and-Xsource-3
branch
from
93c2664
to
595a127
Compare
dwijnand
force-pushed
the
promote-override-nullary-to-2.13-and-Xsource-3
branch
from
595a127
to
6ae3b2a
Compare
SethTisue
added
the
prio:hi
narma
reviewed
May 13, 2020
dwijnand
force-pushed
the
promote-override-nullary-to-2.13-and-Xsource-3
branch
from
6ae3b2a
to
4216bb1
Compare
|
this seems ready for merge, but holding off for now until #8833 is also ready |
|
@dwijnand needs rebase |
SethTisue
removed
the
prio:hi
SethTisue
changed the title
SethTisue
changed the title
|
@dwijnand this is just a lint and not an actual deprecation... right? |
Yeah, I guess? I meant "deprecate" in "phase out" sense. Happy to call it a lint change. |
dwijnand
force-pushed
the
promote-override-nullary-to-2.13-and-Xsource-3
branch
from
4216bb1
to
88e4569
Compare
SethTisue
force-pushed
the
promote-override-nullary-to-2.13-and-Xsource-3
branch
from
88e4569
to
f491020
Compare
Aka "promote -Xlint:override-nullary". This means warn by default & error under -Xsource:3.
dwijnand
force-pushed
the
promote-override-nullary-to-2.13-and-Xsource-3
branch
from
f491020
to
43438a6
Compare
|
@dwijnand could you improve the PR description to document this for folks who don't already know the context/motivation? |
SethTisue
changed the title
SethTisue
changed the title
SethTisue
changed the title
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.
In Scala 3 a method
def foo: A(known as a "nullary" method) cannot override a methoddef foo(): A(recently coined as a "nilary" method - because it contains one, empty parameter list). We now warn in Scala 2.The reverse (overriding
def foo()withdef foo) now also warns. But Java-defined methods are exempt, since Java doesn't have nullary methods but Scala users may wish to override non-side-effecting methods as nullary, for exampleoverride def toString = ....This behavior was already available via
-Xlint:nullary-override, but now warns by default, and errors under-Xsource:3.-Xlint:nullary-overrideis no longer accepted.Strongly related to deprecating auto-application (#8833).