Deep duplicate in deep_merge
so no references remain to the original hash in the result
#41931
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.
Summary
The documentation for
deep_merge
says that a new hash is returned. But when deep merging aHash
with a nestedHash
, the nestedHash
is actually a reference to the original nestedHash
, only a shallow copy is created.This can lead to unexpected modifications when the nested
Hash
of the merged result gets modified.Other Information
Reproduce case: