Fix merge lexical environment to *always* respect prologue statements #24602
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
mhegazy
approved these changes
Jun 2, 2018
|
Please port to release-2.9 as well. |
weswigham
added a commit
to weswigham/TypeScript
that referenced
this pull request
Jun 4, 2018
weswigham
added a commit
that referenced
this pull request
Jun 4, 2018
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 #24582
mergeLexicalEnvironmentonly calledprependStatementswhenstatementswasn't a node array. Specifically in the case of destructuring assignments, it seems like it was an array instead of a node array, causing the difference. NowmergeLexicalEnvironmentusesprependStatementsin both cases.