Should a formal spec be required for phase 3?
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- wasm
调研方向
Start with the phase 2 and phase 3 requirements quoted in the issue, then review the linked Google Docs overview. Compare the current process with the proposed formal-spec requirement. Done means a clear decision on whether to amend the phase 3 requirements, with the process description updated if the proposal is accepted.
由索引模型根据 Issue 内容生成。
描述
The current requirements for phase 2 are:
- Precise and complete overview document is available in a forked repo around which a reasonably high level of consensus exists.
- Updates to the actual spec document, test suite, and reference interpreter are NOT yet required.
The current requirements for phase 3 are:
- Test suite has been updated to cover the feature in its forked repo.
- The test suite should run against some implementation, though it need not be the reference interpreter.
- Updates on the actual spec document and reference interpreter are NOT yet required (but can happen earlier).
The purpose of phase 2 is for at least one engine to implement the feature, enough to produce a reasonable test suite for phase 3. On the other hand, the purpose of phase 3 is for all engines to implement the feature - but they are forced to do so without a formal spec, and must make do with a "precise and complete overview document". Personally, having gone through much of the Wasm GC implementation with nothing to guide me but a linked list of Google Docs, I would have MUCH PREFERRED a formal spec to follow.
I presume the lack of spec requirement was because, in the past, the formal spec was very burdensome to update. But these days much of the tedium is handled by SpecTec and we have AIs that can catch bugs and slog through macro minutia. I find it much easier these days to keep the formal spec up to date.
Should we amend the process to require a complete formal spec by phase 3?
- 主要语言
- Python
- 星标
- 1.1k
- 派生
- 78
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
WebAssembly/proposals 的其他 Issue
-
难度 5/5 一周以上 新手友好度 20/100
WebAssembly/proposals#175 · 2 条评论 ·
-
good first issue help wanted
难度 2/5 1-3 小时 新手友好度 45/100
WebAssembly/proposals#99 · 9 个 reaction ·
-
难度 5/5 一周以上 新手友好度 25/100
WebAssembly/proposals#148 ·
-
难度 5/5 一周以上 新手友好度 20/100
WebAssembly/proposals#68 · 19 条评论 ·
-
难度 5/5 一周以上 新手友好度 25/100
WebAssembly/proposals#21 · 13 条评论 · 14 个 reaction ·
查看 WebAssembly/proposals 的全部 Issue
相似的 Issue
-
Layout accepts a step threshold of 0 or less, then in-toto-verify crashes with StopIteration可能已有人在做 @BahaaMattar 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
needs discussion
难度 2/5 1-3 小时 新手友好度 78/100
openfga/openfga.dev#1436 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
usb-device-hid: MouseInterface reports bInterfaceProtocol 1 (keyboard) instead of 2可能已有人在做 @Duhan07 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
micropython/micropython-lib#1176 ·