Class Declaration Is Automatically In Strict Mode #4070
Merged
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
added 2 commits
April 8, 2015 11:35
vvakame
added a commit
that referenced
this pull request
Apr 12, 2015
Class Declaration Is Automatically In Strict Mode
|
@yuit wow! thanks mate. |
|
No problem :) |
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.
In ES6, class declaration and class expression are considered strict mode code. TypeScript compiler has updated parsing for class declaration and class expression as such. One strict mode restriction is that
argumentsis not allowed as an identifier in parameter declaration. This pull request is to fix usingargumentsin function's parameter