Path to Stage 4

[acutmore]

Stage 4

• committee approval
• two implementations
• significant in-the-field experience
• ecma262 PR approved

Stage 3

• committee approval
• merge test262 tests

Stage 2.7

• committee approval
• spec editor signoff
  • @bakkot
• spec reviewer signoff
  • @ljharb
  • @jasnell

Stage 2

• committee approval
• spec reviewers selected
  • @ljharb
  • @jasnell
• spec text written

Stage 1

• committee approval

[ljharb]

LGTM! Just some minor notes:

• CreateKeyedPromiseCombinatorResultObject presumably shouldn't go under "properties of the promise constructor" - perhaps it should go in https://tc39.es/ecma262/#sec-promise-abstract-operations ?
• allSettledKeyed is a terrible name, but we do need the variant and i understand the convention being applied
• PerformPromiseAllKeyed and PerformPromiseAllSettledKeyed are identical except for 6.b. Is there a refactoring that could be applied to avoid duplicating the other 8ish steps?

[ajvincent]

Congratulations on stage 2.7. I wish I could participate more, but it seems to be moving along well now.

[acutmore]

Thanks @ajvincent! Still 1.3 to go 😃

[linusg]

Implementations are starting to appear:

• https://phabricator.services.mozilla.com/D284151
• feat(promise): implement Promise.allKeyed and Promise.allSettledKeyed boa-dev/boa#4996

[linusg]

Deno implemented this in their standard library (though I'm not sure why given that availability of the Promise builtins is imminent):

• feat(async/unstable): add allKeyed and allSettledKeyed denoland/std#6959
• feat(async): stabilize allKeyed denoland/std#7058