Avoid field/field clashes #14081
Merged
Avoid field/field clashes #14081
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
anatoliykmetyuk
approved these changes
Dec 17, 2021
anatoliykmetyuk
force-pushed
the
fix-13862
branch
from
461d3e8
to
b9e54be
Compare
There needs to be a special alignment of planetary body to obtain two fields that have different names for Dotty (one has a FieldName, the other a regular name), but that still map to the same underlying name. This is now detected and resolved. Fixes scala#13862
anatoliykmetyuk
force-pushed
the
fix-13862
branch
from
b9e54be
to
34e0b4d
Compare
|
I rebased this on |
|
@anatoliykmetyuk Yes, the change is fine. Thanks for the rebase! |
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.
There needs to be a special alignment of planetary bodies to obtain two fields
that have different names for Dotty (one has a FieldName, the other a regular name),
but that still map to the same underlying name. This is now detected and resolved.
Fixes #13862