Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Pre-adoption: language decisions to settle while we are the only users (lessons from other languages' v1 regrets)

オープン
#1,286 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
30/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
c
領域
compilers

調査の方向性

This is a design issue for the language owner, tracking foundational decisions before external adoption. It references the EigenScript codebase, stdlib modules, and builtins. A newcomer would need deep familiarity with language design and the codebase to contribute. The work involves evaluating each lesson (e.g., number types, string model, concurrency) and making decisions, likely leading to separate implementation issues.

索引モデルが issue の本文から書いたものです。

説明

area:runtime-vm kind:decision

When: not a date. v1 follows real external consumers (after Linguist recognition and adoption work). But the day the FIRST outside consumer depends on a behavior, changing it stops being free and needs a migration path. So these decisions should be settled while we are still the only users. (Owner, 2026-09-23.)

Why: researched 2026-09-23 against primary sources. The recurring regrets of other languages, each mapped to where EigenScript stands. Probes were run on main c8288a5.

Lesson EigenScript now To decide
Build the breaking-change escape hatch before you need it. Go retrofitted per-module semantics via the go.mod version line + GODEBUG for the 1.22 loop-variable fix (go.dev/blog/loopvar-preview); Rust added editions (RFC 2052, 2017) two years after 1.0 (Book app. E). eigs.json has name/version, no language-version field. Add a language edition field now, so a post-adoption semantic fix can be opt-in per project.
One overloaded number type later needs a second type bolted on. JS Number → BigInt (proposal). One IEEE double. 9007199254740992 + 1 prints 9007199254740992: silent precision loss past 2^53. An integer type, or raise on precision loss. Silence is the one option to rule out (it is the fail-soft class #975 exists to remove).
Absence/null semantics are a founding decision. Hoare's "billion-dollar mistake"; JS typeof null could not be fixed because code depended on it. null, whose type of is "none"; a separate VAL_JSON_RAW value type. One documented absence model, one name for it.
Booleans folded into another type. 1 == 1 → 1, type of → num. A boolean type, or document numbers-as-truth as permanent.
Remove before you freeze. Python's PEP 594 took three releases to drop dead modules (PEP 594); PHP's haystack/needle order was never unified (RFC). 78 stdlib modules, 209 builtins. Stdlib audit: cut what does not earn its place; a naming/argument-order lint rule while the surface is small.
The string model is the most expensive thing to change later. Python 2→3 (~12 years), Ruby 1.9 M17N (migration notes). Byte strings with UTF-8 helpers. Bytes vs text, and what a "character" is, decided and documented.
Concurrency added late becomes an ABI break. CPython GIL → PEP 703, free-threaded builds ABI-incompatible (PEP 703). Threads/channels exist; hardening is a trail of fixes (#1146, #1173 open). The concurrency safety model written down as a guarantee.
Freeze source semantics before binary contracts (Swift: source churn 1–3, ABI stability at 5 — swift.org). Two binary-shaped contracts: the tape format and the opcode ABI. Version each separately from the language edition.
Deprecation policy once users exist (Python PEP 387, ≥2 releases — PEP 387). None needed yet (no external users). Write it now, to switch on at the first outside consumer.

Each row should become its own kind:decision issue when it is picked up; this issue tracks the set. Semantic decisions (numbers, booleans, absence, strings) are the owner's call; the recommendation in each row is a starting position, not a decision.

Done when

  • Every one of the nine rows has a recorded verdict in a comment here: keep (with the measurement that justifies departing from the mature-language default, per the 2026-09-24 decision rule) or change. Rows: language edition field, number type / precision loss, absence model, boolean type, stdlib audit + naming/argument-order lint, string model, concurrency guarantee, binary-contract versioning (tape format + opcode ABI), deprecation policy.
  • Every change row links its own kind:decision issue (with an area:* label). Already defaulted to change and still without an issue: numbers, booleans, absence, strings, versioning (edition + deprecation policy), stdlib core/packages split.
  • The two rows with no default yet (concurrency guarantee, binary-contract versioning) have a verdict.
  • The stdlib row's issue lists the package system's one-pin rule as a blocker before the first module moves out of lib/.
  • The table in this body carries a "Verdict / issue" column filled for all nine rows, so status reads from the body, not the thread.
主要言語
C
スター
3
フォーク
7
平均マージ
4時間 5分
マージ済み PR(30日)
116

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

InauguralSystems/EigenScript のほかの issue

InauguralSystems/EigenScript の issue をすべて見る

似ている issue

C の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。