Improve side-effect tracking for call arguments #3539
Merged
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.
…tracked side-effects in nested calls
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Resolves #3533
Description
See #3533. In this situation, the tracking logic that is meant to prevent infinite recursions in Rollup's side-effect detection would fire for the inner
.forEach
call expression because it thought this call had already been tracked as it was the same variable and path of the outer.forEach
call. Of course this is not the case, so for call expressions, the recursion prevention logic will now also discriminate based on original call expression and not only variable.