Fix: fix wrong code-path about try-for-in (fixes #8848) #9348
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 is the purpose of this pull request? (put an "X" next to item)
[X] Bug fix (template)
Fixes #8848.
What changes did you make? (Give an overview)
This PR fixes code path analysis to generate correct code paths.
Before, it was wrong if
ForInStatement#right
is the first throwable location (e.g. a variable reference, a call expression, ...) in the outertry
block. (It makes 2 paths fromtry
block tocatch
block at the first throwable location and the end oftry
block. The former seemed to conflict with the looping path offor-in
.)In the following code:
Before: broken code path.
After: correct code path.
Is there anything you'd like reviewers to focus on?
Nothing in particular.