Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correctly preserve reference to array in for-of loop #9697

Merged
merged 2 commits into from Mar 18, 2019
Merged

Correctly preserve reference to array in for-of loop #9697

merged 2 commits into from Mar 18, 2019

Conversation

danez
Copy link
Member

@danez danez commented Mar 17, 2019

Q                       A
Fixed Issues? Fixes #9696 Fixes #8913 Fixes #8920
Patch: Bug Fix? y
Major: Breaking Change? n
Minor: New Feature? n
Tests Added + Pass? Yes
Documentation PR Link
Any Dependency Changes?
License MIT

This change ensures that the reference to an array inside the header of an for-of loop cannot be unset.

@danez danez added the PR: Bug Fix 🐛 A type of pull request used for our changelog categories label Mar 17, 2019
@babel-bot
Copy link
Collaborator

babel-bot commented Mar 17, 2019

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/10508/

@danez danez requested a review from loganfsmyth March 17, 2019 20:32
@@ -1,11 +1,13 @@
const x = [];
var _arr = x;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to move this inside the for head?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes i actually did that, but it changes a lot of tests. Would do it separate.

@danez danez merged commit f36a698 into babel:master Mar 18, 2019
@danez danez deleted the fix-arr-for-of-scope branch March 18, 2019 04:41
@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Oct 4, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue PR: Bug Fix 🐛 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrong behavior of for of loop for...of array optimization can introduce conflicting variables into the scope
4 participants