Stage 3 and 4 roadmap

[nicolo-ribaudo]

Pending from Stage 2.7

Stage 2.7 was conditional on the editors finishing reviewing the spec text. As far as I'm concerned the proposal is now in its final shape, so this is a good time to review it :)

• Editor reiviews
  • @bakkot
  • @michaelficarra (already approved in Stage 2.7 roadmap #24, but feel free to un-tick if you'd like to re-review given the recent changes)
  • @syg

Stage 3

• test262 (import defer testing plan test262#4215)
  • Add partial tests for import defer Add partial tests for import defer test262#4278
  • Add test for @@toStringTag on deferred module namespaces Add test for @@toStringTag on deferred module namespaces test262#4360
  • Update import defer tests for evaluation triggers Update import defer tests for evaluation triggers test262#4341
  • Add syntax tests for import.defer Add syntax tests for import.defer test262#4374
  • Add evaluation tests for import.defer with sync/async modules Add evaluation tests for import.defer with sync/async modules test262#4375

Stage 4

• ECMA-262 PR
• Two implementations
  • JSC (parsing support: [JSC] Add parsing for deferred import proposal WebKit/WebKit#36664)
  • SM
  • V8

[ljharb]

I believe the actual reviewers need to approve/reaffirm as well, not just the editors.

[guybedford]

Just did another review of the spec text and can confirm everything continues to look good to me.

One minor change I'd suggest using 16.2.1.10 GetModuleNamespace ( module, deferred ) with deferred as a boolean instead of the GetModuleNamespace( module, phase ) taking a phase argument, since we don't anticipate defining other variations of module namespaces at other phases.