Path to Stage 4!
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- web-dev
Research direction
This issue is a Stage 4 progress checklist rather than a single code change. Start with the linked test262 plan and tests, implementation reports for JavaScriptCore, SpiderMonkey, XS, and V8, and the ecma262 references. Done means the remaining proposal-stage requirements and feedback items are resolved.
Written by the indexing model from the issue text.
Description
Stage 4
- committee approval
- two implementations
- significant in-the-field experience
- ecma262 PR approved
- prepare ecma262 PR
Stage 3
- committee approval
- merge test262 tests
- write test262 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
.immutablefor easy upgrade. Resolved and closed
- #9
- Yes. Resolved and closed
- #16
- Purposely left open for more implementor feedback
- #15
- status of non-normative issues
- #25
- No. This proposal not applicable to WebGPU, but Limited ArrayBuffer may be.
- #19
- #18
- Mixed bag. See Prior proposals or issues with overlapping goals
- #26
- #25
- 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
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tc39/proposal-immutable-arraybuffer
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tc39/proposal-immutable-arraybuffer#43 · 2 comments ·
-
Review Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
tc39/proposal-immutable-arraybuffer#30 · 12 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
tc39/proposal-immutable-arraybuffer#18 · 1 comment ·
All issues in tc39/proposal-immutable-arraybuffer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·