docs: one authoritative spec (SPEC / LANGUAGE_CONTRACT / GRAMMAR / SYNTAX overlap)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
调研方向
The issue mentions four documents in the docs/ directory: SPEC.md, LANGUAGE_CONTRACT.md, GRAMMAR.md, and SYNTAX.md. Start by reading these files to understand their current content and overlaps. Look for duplicated normative statements. The goal is to consolidate them into one authoritative spec, ensuring all executable examples still run and updating references in llms.txt and the mentioned skills.
由索引模型根据 Issue 内容生成。
描述
Problem. Four documents cover overlapping ground on what the language IS: docs/SPEC.md (2,272 lines), docs/LANGUAGE_CONTRACT.md, docs/GRAMMAR.md and docs/SYNTAX.md. Overlap means copies, and copies disagree. The 2026-09-22 prompt audit found write-eigenscript teaching three semantics the language had since changed (loop-body scope, observer keying, constant convergence), because it summarised a copy rather than the contract.
What mature languages do. There is exactly one authoritative specification, separate from the tutorial: the Go spec (a single page), Python's Language Reference, the Rust Reference.
Bar.
- One document is THE spec. It carries the grammar (or includes GRAMMAR by reference) and the contract rules. Every normative statement lives there exactly once.
- The other three are either folded in, or turned into explanation that links to spec sections instead of restating them. Checked: no normative rule text appears in two documents (a duplication grep, or the docs-claims NAMES class).
- Every executable example in the merged spec still runs.
llms.txtand thewrite-eigenscript/eigenscript-lang-reviewskills point at the one spec.
Ranked #4 of the docs follow-ups (2026-09-22 comparison with other languages).
- 主要语言
- C
- 星标
- 3
- 派生
- 7
- 平均合并
- 3 小时 56 分钟
- 30 天内合并 PR
- 102
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
InauguralSystems/EigenScript 的其他 Issue
-
area:lint-tooling bug
难度 2/5 1-3 小时 新手友好度 88/100
InauguralSystems/EigenScript#1340 ·
维护者通常 1 天内回复
-
area:stdlib found-by:code-review kind:silent-wrong
难度 2/5 1-3 小时 新手友好度 88/100
InauguralSystems/EigenScript#1338 ·
维护者通常 1 天内回复
-
area:lint-tooling found-by:critic kind:docs-drift
难度 2/5 1-3 小时 新手友好度 76/100
InauguralSystems/EigenScript#1335 ·
维护者通常 1 天内回复
-
area:ci found-by:critic kind:gate-defect
难度 2/5 1-3 小时 新手友好度 86/100
InauguralSystems/EigenScript#1311 ·
维护者通常 1 天内回复
-
enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchet未关闭area:gates found-by:critic kind:decision
难度 2/5 1-3 小时 新手友好度 65/100
InauguralSystems/EigenScript#1280 · 1 条评论 ·
维护者通常 1 天内回复
查看 InauguralSystems/EigenScript 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
libretro/libretro-common#233 ·
-
[Bug]: chunk_span_bounds and _validated_chunk_spans reject Pydantic models ChunkSpan and AudioFile未关闭
难度 2/5 1-3 小时 新手友好度 78/100
BasedHardware/omi#19047 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 76/100
obsproject/obs-studio#13936 · 2 条评论 ·
维护者通常 1 天内回复