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

Port fix for bad binding of async arrow function parameters #2219

Merged
merged 1 commit into from
Dec 16, 2016

Conversation

pleath
Copy link
Contributor

@pleath pleath commented Dec 16, 2016

Apply the same parse-time-binding logic to async arrow function parameter lists as to normal arrow function parameter lists. (They take different paths in the parser prior to the discovery of the arrow.)

@chakrabot chakrabot merged commit c663ea8 into chakra-core:release/1.3 Dec 16, 2016
chakrabot pushed a commit that referenced this pull request Dec 16, 2016
…n parameters

Merge pull request #2219 from pleath:1612_1.3

Apply the same parse-time-binding logic to async arrow function parameter lists as to normal arrow function parameter lists. (They take different paths in the parser prior to the discovery of the arrow.)
chakrabot pushed a commit that referenced this pull request Dec 16, 2016
…ow function parameters

Merge pull request #2219 from pleath:1612_1.3

Apply the same parse-time-binding logic to async arrow function parameter lists as to normal arrow function parameter lists. (They take different paths in the parser prior to the discovery of the arrow.)
chakrabot pushed a commit that referenced this pull request Dec 16, 2016
… of async arrow function parameters

Merge pull request #2219 from pleath:1612_1.3

Apply the same parse-time-binding logic to async arrow function parameter lists as to normal arrow function parameter lists. (They take different paths in the parser prior to the discovery of the arrow.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants