fix: defer lookaheadState to Babel 8 #13383
Closed
Conversation
This file contains 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
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/46501/ |
JLHwung
commented
May 27, 2021
| inType: state.inType, | ||
| }; | ||
| if (process.env.BABEL_8_BREAKING) { | ||
| const { pos, type, start, end, exprAllowed, inType } = state; |
There was a problem hiding this comment.
Use destructuring here to avoid double object access (state.end) and redundant object slot initialization, see #13341 (comment)
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 10663eb:
|
|
Closed in favor of #13382 |
github-actions
bot
added
the
outdated
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #1, Fixes #2Recently we have seen CI errors from Node.js 6. It is likely a crankshaft bug, which is gone when crankshaft is replaced by Ignition and TurboFan in later Node versions. I don't think it is worthy to spend time on this bug, so let's defer #13341 to Babel 8.