Revive for..of optimization #4208
Closed
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.
This revives the effort for us to use ES6 features without sacrificing performance.
We'll transpile
for..of
statements toThere's a potential optimisation in here to extract
x.length
outside of the loop so we don't have to accesslength
every time. Another thing we'll have to transpile is array destructuring.With the automated approach like here we'll still have a lot of
for..of
where we invoke the iterator of i.e. a map.Related to #3691