Path to Stage 4!

[ljharb]

Stage 4

• committee approval
• two implementations
  • WebKit, behind a flag and with arg forwarding (PR) - no longer behind a flag (PR)
  • Keisel
  • Boa
  • LibJS
  • Chrome / v8 (v128)
  • Firefox / spidermonkey issue issue 2 (behind a flag in v132 nightly, targeted for 133 or 134 unflagged)
  • Bun (tweet)
  • CloudFlare Workers (tweet
• significant in-the-field experience
• ecma262 PR approved
• prepare ecma262 PR (PR)

Stage 3

• merge test262 tests
• write test262 tests (PR)
• receive implementer feedback

Stage 2.7

• committee approval
• spec editor signoff
  • @syg
  • @bakkot
  • @michaelficarra
• spec reviewer signoff
  • @gibson042
  • @rkirsling
• spec reviewers selected
• answer open questions
  • Passing arguments to the function #9 / [spec] accept optional arguments to pass to the callback #16

Stage 2

• incorporate enumeration (✨ stage 2 #17)
• committee approval
• spec text written

Stage 1

• committee approval

[rkirsling]

LGTM overall; my one comment would be that maybe we should include the NOTE attached to Promise.resolve here too.

[ljharb]

Thanks, done in fdb9bd2

[rkirsling]

Went ahead and implemented it in JSC right away: WebKit/WebKit@6d51d57

[syg]

Editorially, spec draft lgtm.

Normatively, I'd like #16 merged (which also lgtm).

[bakkot]

LGTM with #16.

[michaelficarra]

LGTM

[linusg]

Implemented in Kiesel: https://codeberg.org/kiesel-js/kiesel/commit/5e215d3dc8839768960343f4ca7e2764c188828a

[linusg]

This was so simple that I decided to implement it in two more engines :)

• Boa: Implement Promise.try() boa-dev/boa#3800
• LibJS: LibJS: Implement Promise.try() SerenityOS/serenity#23898

[gibson042]

I have reservations about Promise.try accepting variadic arguments that leave no room for ever specifying a receiver—setting it apart from Function.prototype.{apply,call} and Reflect.apply. However, they do not rise to the level of a blocking concern. Consider this a signoff from me.

[jridgewell]

I have reservations about Promise.try accepting variadic arguments that leave no room for ever specifying a receiver—setting it apart from Function.prototype.{apply,call} and Reflect.apply.

AsyncContext is also doing this for our run methods, so this won't be the only one.