MetadataStorage
is mutable - structural equals in copy
isn't enough
#11513
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.
Pull Request Description
MetadataStorage
is mutable. UsingObject.equals
inIR.copy
methods to check whether a copy is needed isn't enough. The fact that two storages areObject.equal
may be just temporary. Replacing the checks in 69IR.copy
methods with identity check - e.g.ne
in Scala which is==
in Java.Using proper structural check inside of
MetadataStorage
fixes #11171.Important Notes
I used this regex to find out 69 instances of
IR.copy
:and I modified all 69 of them.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Scala,
Java,
MetadataStorage.equals