Update special cases for await / yield expression parsing#16213
Merged
DanielRosenwasser merged 1 commit intoJun 15, 2017
Conversation
This was referenced Jun 2, 2017
Member
|
👍 thanks! |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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 #15943 and #15981
Updated special-case handling for
yieldexpressions outside of generators to parse string literals as yield expressions as well, allowing the type checker to produce a more useful error message in that case. Additionally, updated the special-case handling forawaitexpressions to use the same heuristics asyieldexpressions.