New Strategic Initiative on Primordials
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- javascript
调研方向
首先阅读链接的 TSC issue 1438 和 Node issue 18795，然后查看这里的讨论，以了解现有的 primordials 保证和分歧。当 TSC 批准提案中所述的用例和 CI 测试、文档指导、执行建议以及 TC39 的立场后，这项工作就完成了。
由索引模型根据 Issue 内容生成。
描述
Primordials are a way we use to add robustness to certain areas in our code and there has been a lot of debate about whether or not the issues they create regarding performance and ease of contribution are worth it in different contexts.
Context: https://github.com/nodejs/TSC/issues/1438 https://github.com/nodejs/node/issues/18795
I'd like to proposes a (ideally short lived) new strategic initiative around deciding their status in the project.
I'm happy to drive this as a strategic initiative if there is interest from the TSC with the following format:
- We (all members invited) will meet a few times to write use cases and then derive tests from those use cases that will run during CI to enforce we don't break any primordials guarantees (e.g exit handler) . We will try to keep the scope small.
- We will add a warning to the docs outlining the robustness model regarding primordials and what guarantees Node makes. We will make a recommendation and an official "Node wants X" for TC39 discussion.
- We will recommend where to enforce primordials and where not to enforce them and what the PR flow around them should be.
- The TSC will approve every step above either by consensus (good) or by vote (bad).
- All this should happen in the timespan of a month or two, ideally. We rush nothing, hear everyone out and adapt/amend when needed.
I would really like it if collaborators who have spent a lot of time thinking about this participate, namely @aduh95 , @ronag @joyeecheung and @anonrig but there are a lot of others here like @isaacs and @ljharb that are welcome too weigh in and participate.
I think our opinions don't differ that much honestly and I think once we iron out the specifics we can come to a good resolution.
- 主要语言
- JavaScript
- 星标
- 693
- 派生
- 143
- 平均合并
- 8 天 7 小时
- 30 天内合并 PR
- 3
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nodejs/TSC 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 20/100
-
tsc-agenda
难度 5/5 一周以上 新手友好度 8/100
-
难度 5/5 一周以上 新手友好度 3/100
-
build-agenda tsc-agenda
难度 5/5 一周以上 新手友好度 5/100
-
难度 1/5 1 小时以内 新手友好度 18/100
相似的 Issue
-
Energy flow: add an "Other" row so the consumers add up to the consumption total可能已有人在做 @github-actions 今天认领。 未关闭enhancement
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
-
Impact: Medium Level: Easy Type: Bug Value: Users
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 82/100
NobiResearch/Ovenbird#148 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 78/100
glossyio/traffic-monitor#264 ·
维护者通常 1 天内回复
-
balance good first issue
难度 2/5 1-3 小时 新手友好度 75/100
tobeficv/founders-way#5 ·