Test final object is indeed redundant: objects must be JVM-final
#5745
Conversation
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
Blaisorblade
added
stat:needs review
fasttrack
smarter
approved these changes
Jan 18, 2019
| @Test def objectsAreFinal = { | ||
| val source = | ||
| """class Test { | ||
| | object Foo |
There was a problem hiding this comment.
I would test a few more cases (top-level object, object in object, object in local block).
Blaisorblade
force-pushed
the
test-objects-are-final
branch
from
5dcc31d to
e239918
Compare
Scalac sometimes *forgets* the final bytecode flag, and sometimes one cares, so people even *recommend* always writing *final object* instead of object. That's bad, since we started warning about it in scala#4973. scala/bug#11094 (comment) https://nrinaudo.github.io/scala-best-practices/adts/final_case_objects.html Why care? ========= If we forget the final flag in bytecode, Java code might then extend the class. Performance might or might not be affected - some in scala/contributors debated this for ~20 minutes (starting at https://gitter.im/scala/contributors?at=5c423c449bfa375aab21f2af).
Blaisorblade
force-pushed
the
test-objects-are-final
branch
from
e239918 to
29e1f8a
Compare
smarter
approved these changes
Jan 19, 2019
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.
Scalac sometimes forgets the final bytecode flag, and sometimes one cares, so
people even recommend always writing final object instead of object. That's
bad, since we started warning about it in #4973.
scala/bug#11094 (comment)
https://nrinaudo.github.io/scala-best-practices/adts/final_case_objects.html
Why care?
If we forget the final flag in bytecode, Java code might then extend the class.
Performance might or might not be affected - some in scala/contributors
debated this for ~20 minutes (starting at
https://gitter.im/scala/contributors?at=5c423c449bfa375aab21f2af).