Process requirement for sufficient demand
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
调研方向
从 issue #68 开始,阅读完整的评论线程,包括编辑后的提案以及关于 Stage 3 要求的讨论。完成意味着就每项 Stage 3 功能是否都应要求有大量用户群需求作出并记录决定;payload 未列出要运行的文件或测试。
由索引模型根据 Issue 内容生成。
描述
WebAssembly has a significant backwards compatibility constraint. It is also exploring an almost entirely new space and solving very hard problems requiring substantial design and implementation work. As such, it is important to make sure that any designs developed, implemented, and shipped have been substantially evaluated on whether they achieve their intended purpose. To this end, I suggest the following amendment to the process:
As a requirement for advancing to Stage 3, every feature of the proposal should have approval from a substantial user base (where the appropriate scale/meaning of "substantial" and "user base" depends on the specifics of the proposal).
There are two primary reasons for this revision:
- We cannot evaluate whether the proposal's design for a feature effectively achieves its intended goal without a substantial user base to either demonstrate its utility or to provide feedback on how the proposal needs to be revised to meet their needs.
- As much of that evaluation should be done prior to implementation to reduce churn due to design changes.
With this requirement in place, when the reference types proposal went to Stage 3 we would have seen that, although external references had a big user base, subtyping did not and so should be carved out into a separate proposal. Furthermore, this separation would have made it apparent that many other proposals do not need to depend on the reference types proposal. Many uses of type imports do not need any constraints at all (arguably external references are an example of this), and alternative (even more expressive) constraints besides subtyping could be explored. Although exception handling uses exnref, which might represent uninterpretable exceptions depending on the host, there is no requirement that exnref be related to external references. Even garbage collection does not depend on anyref or external references; we demonstrated that even languages relying on a uniform representation would generally prefer to use a uniform representation that is specialized to the needs of the language over a useless type like anyref. So the separation this requirement would have encouraged would have also reduced the dependencies between proposals.
But pulling back from the current situation, what do y'all think of the proposed revision that every feature of a Stage 3 proposal should have enough demand to warrant implementation and to enable proper evaluation?
[This was substantially edited thanks to feedback from @jgravelle-google.]
- 主要语言
- Python
- 星标
- 1.1k
- 派生
- 78
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
WebAssembly/proposals 的其他 Issue
-
难度 5/5 一周以上 新手友好度 35/100
WebAssembly/proposals#243 · 5 条评论 · 4 个 reaction ·
-
难度 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 一周以上 新手友好度 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 ·