Removed lookahead for simple arrow function expressions. #460
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
|
👍 |
2 similar comments
|
👍 |
|
👍 |
ahejlsberg
added a commit
that referenced
this pull request
Aug 15, 2014
Removed lookahead for simple arrow function expressions.
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.
The parser currently performs a look-ahead on every expression that starts with an identifier to determine if an
=>token follows. This commit reverts back to the original design of recognizing an expression consisting of a single identifier to the left of an=>token and then treating that identifier as a parameter list. This reduces the overall number of look-aheads performed by the scanner by over 30%.