β‘ Bolt: Optimize deep_merge with in-place mutation #498
+59
β10
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.
π‘ What: Optimized
deep_mergeto use in-place mutation instead of full structure cloning.π― Why:
deep_mergepreviously cloned the entire baseserde_yaml::Valuemap at every level of recursion, even for keys that weren't being modified. This caused unnecessary memory allocation and copying, O(N) for every merge operation.π Impact: significantly reduces memory allocations and copying overhead for variable merging, especially when
hash_behaviour = mergeis used or when merging deep structures.π¬ Measurement: Validated with unit tests ensuring behavior remains identical to the original implementation.
PR created automatically by Jules for task 14665495014126406948 started by @dolagoartur