Path to Stage 4!

Stage 4

• committee approval
• two implementations
  • JavaScriptCore
  • SpiderMonkey (progress)
  • XS
  • V8
• significant in-the-field experience
• ecma262 PR approved
• prepare ecma262 PR

Stage 3

• committee approval
• merge test262 tests
• write test262 tests
  • testing plan
  • basic tests
• receive implementer feedback
  • XS: implemented, tested, all good
• resolve all normative stage 4 issues
  • #44
  • #16 was not a normative requirement for 2.7. It is normative for stage 3

Stage 2.7

• committee approval
• spec editor signoff (@tc39/ecma262-editors)
  • Shu-yu Guo (@syg) (see #30)
  • Kevin Gibbons (@bakkot) (see https://github.com/tc39/proposal-immutable-arraybuffer/issues/31#issuecomment-2663380344)
  • Michael Ficarra (@michaelficarra) (verbally deferred to @syg and @bakkot)
• spec reviewer signoff
  • Shu-yu Guo (@syg) (see #30)
  • Waldemar Horwat (@waldemarhorwat) (see #41)
  • Jordan Harband (@ljharb) (see https://github.com/tc39/proposal-immutable-arraybuffer/issues/27#issuecomment-2661069560)
• resolve all normative issues
  • #15
    • Yes. Resolved and closed
  • #10
    • .immutable for easy upgrade. Resolved and closed
  • #9
    • Yes. Resolved and closed
  • #16
    • Purposely left open for more implementor feedback
• status of non-normative issues
  • #25
    • No. This proposal not applicable to WebGPU, but Limited ArrayBuffer may be.
  • #19
    • Yes. See https://github.com/whatwg/html/pull/11033
  • #18
    • Mixed bag. See Prior proposals or issues with overlapping goals
  • #26
    • Yes. See https://github.com/endojs/endo/pull/2688
• receive implementer feedback
  • XS implementation good. Does not suggest any changes.
  • shim implementation and practical use is necessarily incomplete, but does not suggest any changes.
  • others...?

Stage 2

• committee approval
• spec reviewers selected
  • Shu-yu Guo (@syg)
  • Waldemar Horwat (@waldemarhorwat)
  • Jordan Harband (@ljharb)
• spec text written

Stage 1

• committee approval

Este issue es una lista de comprobación del progreso de Stage 4, no un único cambio de código. Empieza con el plan y las pruebas de test262 enlazados, los informes de implementación para JavaScriptCore, SpiderMonkey, XS y V8, y las referencias de ecma262. Se considera terminado cuando se hayan resuelto los requisitos y los puntos de feedback restantes de la fase de propuesta.