build/npm: add TS transformation that optimise for-of on arrays #3691
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for compassionate-pike-271cb3 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Hi @IvanGoncharov, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
Closed
Context: I wanted to try more automatic alternative to graphql#3687 that allows us to continue using ES6 features without perfomance lost.
IvanGoncharov
force-pushed
the
fast-for-of
branch
from
4e747da to
d1dea90
Compare
|
@IvanGoncharov https://astexplorer.net/#/gist/54f452efefc94d565223d4296a91172e/84b9951249ac82a140e5aeafa3bec78c9861dd96 this would do the array destruct optimizations |
|
@JoviDeCroock do you know the status of this one by any chance? |
|
@yaacovCR I don't no |
|
Closing in favor of #4208 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context: I wanted to try more automatic alternative to #3687 that
allows us to continue using ES6 features without perfomance lost.