Brummel
72e54f4fd3
The surface-form file extension changes from .ailx to .ail. AILang's
authoring surface now uses the same .ail stem as its canonical JSON
form (.ail.json), giving the language a single coherent extension
family: .ail is the LLM-authored Form A, .ail.json is the canonical
JSON-AST Form B.
Scope (touched):
- 61 example renames examples/**/*.ailx → .ail (git mv)
- 1 rename experiments/.../rendered/ailx.md → ail.md
- 35 content-edited live-toolchain files (crates/, docs/DESIGN.md,
docs/roadmap.md, docs/PROSE_ROUNDTRIP.md, skills/, bench/reference/*.c,
experiment crates under experiments/.../{render,harness,master})
- Experiment-crate cohort rename Cohort::Ailx → Cohort::Ail,
Form::Ailx → Form::Ail, per_cohort/ailx → per_cohort/ail,
{form-only: ailx} → {form-only: ail}, ```ailx → ```ail
Out of scope (deliberately untouched, to preserve honest history):
- docs/journal-archive.md (content-frozen per CLAUDE.md)
- docs/journals/, docs/specs/, docs/plans/, bench/orchestrator-stats/
- experiments/.../runs/ (frozen LLM-output artefacts; models actually
saw .ailx — renaming would falsify the experimental record)
Verification: cargo build/test --workspace green; experiment crate
cargo test green; bench/check.py + compile_check.py + cross_lang.py
all 0-regressed; negative grep for ailx|Ailx|AILX outside the
out-of-scope paths returns zero matches.
Opens immediate follow-up: roadmap.md P2 todo `ail check`/build/run
accept .ail extension — after this rename, .ail is canonical
authoring surface but the CLI still produces a misleading JSON-parse
error on `ail check foo.ail`. That's the next iter.
36 lines
1.3 KiB
Plaintext
36 lines
1.3 KiB
Plaintext
; Iter 16d — `__unreachable__` as an explicit user-callable primitive.
|
|
; Type: forall a. a (lowered to LLVM `unreachable`).
|
|
;
|
|
; This fixture exercises `__unreachable__` in a value position that is
|
|
; statically unreachable but still type-checks: the impossible branch
|
|
; of an if. `safe_div(a, b)` returns `a / b` when `b != 0` and panics
|
|
; via `__unreachable__` otherwise. The driver only ever calls it with
|
|
; non-zero divisors, so the panic branch is never executed.
|
|
;
|
|
; The point of the fixture is the type-system + codegen surface:
|
|
; `__unreachable__` unifies against `Int` (the fn's return type) at
|
|
; the typechecker, and codegen lowers it to `unreachable` followed by
|
|
; the rest of the if's join machinery, which is sound because the
|
|
; surrounding if's `block_terminated` flag is honoured.
|
|
;
|
|
; Expected stdout (one per line): 4, 5.
|
|
|
|
(module unreachable_demo
|
|
|
|
(fn safe_div
|
|
(doc "a/b for b != 0; otherwise panic via __unreachable__.")
|
|
(type (fn-type (params (con Int) (con Int)) (ret (con Int))))
|
|
(params a b)
|
|
(body
|
|
(if (app == b 0)
|
|
__unreachable__
|
|
(app / a b))))
|
|
|
|
(fn main
|
|
(doc "Drive safe_div with non-zero divisors. Expected: 4, 5.")
|
|
(type (fn-type (params) (ret (con Unit)) (effects IO)))
|
|
(params)
|
|
(body
|
|
(seq (do io/print_int (app safe_div 8 2))
|
|
(do io/print_int (app safe_div 15 3))))))
|