RFC: React Expressions with Explicit Generator Expression Semantics #99
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.
RFC: React Expressions with Explicit Generator Expression Semantics
For more background on this proposal, please refer to #98.
In that thread, there was a lot of backlash for the implicit nature of the do-generator by unifying it with the current
{}
JSX expression syntax. This proposal makes it explicit by using the*{...}
syntax for generator expressions. So all the old goodies will be kept:But more adventurous users will be able to use the following syntax for generator expressions:
The Generator Expressions proposal is here: https:/sebmarkbage/ecmascript-generator-expression.
Try it out (CodePen Examples)
Caveats
Strings in
JSXText
with a*
immediately before a left brace will be parsed as aJSXGeneratorExpression
.