Java fields don't override each other #8158
Merged
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
While we model Java fields are overridable from Scala (which is questionable, because clients can still access the field in the super class), we definitely shouldn't treat them as such for pairs of Java owners.
retronym
commented
Jun 19, 2019
| found : String | ||
| required: Array[Int] | ||
| override var counts: String = "" | ||
| ^ |
There was a problem hiding this comment.
This tests the status quo, but I'm not sure that it's even sensible to let Scala vars claim to override Java fields.
adriaanm
approved these changes
Jun 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.
While we model Java fields are overridable from Scala (which is
questionable, because clients can still access the field in the
super class), we definitely shouldn't treat them as such for
pairs of Java owners.
Fixes scala/bug#11575