Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

docs: one authoritative spec (SPEC / LANGUAGE_CONTRACT / GRAMMAR / SYNTAX overlap)

Abierto
  • ¿Algo no está bien?
#1,271 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Área
documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:docs kind:decision

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.

  1. 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.
  2. 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).
  3. Every executable example in the merged spec still runs.
  4. llms.txt and the write-eigenscript / eigenscript-lang-review skills point at the one spec.

Ranked #4 of the docs follow-ups (2026-09-22 comparison with other languages).

Lenguaje dominante
C
Estrellas
3
Forks
7
Merge medio
3 h 58 min
PR fusionados (30 d)
105

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de InauguralSystems/EigenScript

Todos los issues de InauguralSystems/EigenScript

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.