Fix compiled / source generated lazy loop stack handling #68138
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.
When a lazy loop has completed iterations but then ends up failing, and the thing it's looping around has no backtracking constructs, we're incorrectly leaving some state associated with the loop on the backtracking stack. That matters if something earlier in the expression will backtrack and pop associated state from the stack, as it could read the lazy loop's leftover state instead of its own.