Open
Conversation
guybedford
force-pushed
the
update-readme
branch
from
990f3d2 to
a2097d0
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This expands the semantics section of the proposal readme to more clearly cover the proposal semantics in more detail with examples.
The feedback in the past has been that the semantics are hard to understand without an explainer so the hope is that this can fill some of that role, while the test-262 test suite can assist with the technical details.
The aim here being to more easily resolve questions like in #53.
Note that the semantics described here are based on the normative change #58 so this won't land until we determine if we want to land that first.
// cc @legendecas as you were curious to see more information on the exact semantics