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

Fix call syntax after class expression syntax #1468

Merged
merged 1 commit into from Aug 19, 2016

Conversation

ianwjhalliday
Copy link
Collaborator

@ianwjhalliday ianwjhalliday commented Aug 19, 2016

Call syntax was being disallowed after a call expression. Appears to be
a mistake, perhaps copy and paste error. Fix by simply remove line
disallowing call syntax in class expression parsing.

Fixes #1465

Call syntax was being disallowed after a call expression.  Appears to be
a mistake, perhaps copy and paste error.  Fix by simply remove line
disallowing call syntax in class expression parsing.

Fixes chakra-core#1465
@ianwjhalliday
Copy link
Collaborator Author

@Microsoft/chakra-es
@tcare or @suwc

@suwc
Copy link

suwc commented Aug 19, 2016

:shipit:

@tcare
Copy link
Contributor

tcare commented Aug 19, 2016

Looks good.

@chakrabot chakrabot merged commit 6f91c8b into chakra-core:master Aug 19, 2016
chakrabot pushed a commit that referenced this pull request Aug 19, 2016
…yntax

Merge pull request #1468 from ianwjhalliday:fix1465

Call syntax was being disallowed after a call expression.  Appears to be
a mistake, perhaps copy and paste error.  Fix by simply remove line
disallowing call syntax in class expression parsing.

Fixes #1465
@ianwjhalliday ianwjhalliday deleted the fix1465 branch August 23, 2016 20:53
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.

None yet

5 participants