Path to Stage 4!

[ljharb]

Stage 4

• committee approval
• class fields is stage 4
• two implementations
  • Firefox (shipped in v90)
  • Chrome (shipped in v91)
  • Webkit Nightly (commit, slated for next STP)
  • Safari (bug)
  • node v16.4+
  • babel (package)
• significant in-the-field experience
• ecma262 PR approved
• prepare ecma262 PR (based on top of Normative: Add public and private class fields, static class features, private methods & getters/setters ecma262#1668)
• merge test262 tests
• write test262 tests (PR)

Stage 3

• committee approval
• spec editor signoff (@michaelficarra, since the other editors are a champion or stage 2 reviewers)
• spec reviewer signoff
  • @waldemarhorwat (pending spec text)
  • @bakkot (pending spec text)
  • @syg
• receive implementor feedback

Stage 2

• committee approval
• spec reviewers selected: @waldemarhorwat, @bakkot, @syg
• spec text written

Stage 1

• committee approval

[michaelficarra]

@ljharb You'll need to add the new alternative in each of the SDOs defined over RelationalExpression. What's there LGTM though.

[syg]

Contents lgtm.

[waldemarhorwat]

So far this seems fine to me but I'd also want to check it against the base proposal. Is there a rendered version of tc39/ecma262#1668 ? Rendering of that one seems to have failed.

[littledan]

@waldemarhorwat tc39/ecma262#1668 has now been rebased, thanks to @Ms2ger . You can find a rendered version at https://arai-a.github.io/ecma262-compare/?pr=1668 (thanks, @arai-a!)

[jugglinmike]

@ljharb I'd be happy to write the Test262 tests. Can you let me know if that's already underway?

[ljharb]

@jugglinmike that would be awesome. I haven’t had time to start yet, and i wasn’t sure what the best way would be wrt the generated tests.

[jugglinmike]

Cool. I'll let you know when the patch is up for review

[jugglinmike]

Here's that patch: tc39/test262#2963

[ljharb]

This proposal is now stage 4!

tc39/proposals@0e01f7e