Fix deep-cloning of subroutiens and modules (fix #174) #175
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.
As the title implies, we were indeed not rebuilding nested
ScopedNode
objects in the duplicationTransformer
used for deep-copying (cloning) ofSubroutine
/Module
objects. This PR fixes this and adds tests that include nestedScopedNode
objects (Associate
for subroutine andTypeDef
for modules) in the duplicated IR.This should fix issue #174.
Many thanks to @JoeffreyLegaux for reporting and providing the reproducer for the subroutine case. I've slightly shortened the example code, but in essence it's the same problem. 😉 Please do confirm that this fixes things as you'd expect.