-
Notifications
You must be signed in to change notification settings - Fork 59
Spec text structure & Attempt at grammar #95
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a good initial outline. I'm looking forward to seeing more of it filled in. I guess there will need to be a section about Record/Tuple exotic objects analogous to https://tc39.es/ecma262/#sec-string-exotic-objects .
</emu-note> | ||
</emu-clause> | ||
<emu-clause id="sec-record-type"> | ||
<h1>Record type</h1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Record value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@littledan It seems that it should be Record value here, but a "Record type" should be a "Record object" below
</emu-note> | ||
</emu-clause> | ||
<emu-clause id="sec-record-type"> | ||
<h1>Record type</h1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@littledan It seems that it should be Record value here, but a "Record type" should be a "Record object" below
Co-Authored-By: Sergey Rubanov <chi187@gmail.com>
This PR structures the proposal's spec text around ECMA262's structure.
Additionally this creates a tentative grammar
Draft is up here: http://tc39.es/proposal-record-tuple/