Improve for loop explosion success with deferred tokens #1048
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.
Now that we have better tracking of the PrefixToPreserveState, we can separate the collection expression execution from the iterating of the for loop.
This leads to better explosion success where we can now support exploding for loops even when there are modifications inside for loops with deferred tokens
Additionally, for loop evaluation will be faster as we don't need to re-run the for loop.
For this input:
Previously, we'd have this output:
But now we can get this exploded output: