Skip to content
This repository was archived by the owner on Apr 15, 2025. It is now read-only.

Conversation

rricard
Copy link
Member

@rricard rricard commented Mar 3, 2020

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/

Copy link
Member

@littledan littledan left a 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>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Record value?

Copy link
Member

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>
Copy link
Member

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>
@rricard rricard merged commit e4559a1 into master May 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants