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.
44 lines
1.7 KiB
Plaintext
44 lines
1.7 KiB
Plaintext
; Iter 16b.5 — LetRec name as value, with capture. A recursive
|
|
; helper `factorial_plus` captures the outer fn-param `base` and is
|
|
; passed as a VALUE to a higher-order combinator. The lifted fn has
|
|
; signature `factorial_plus$lr_N(n: Int, base: Int) -> Int`. The
|
|
; eta-Lam wrap binds `factorial_plus` in the in-clause to a
|
|
; `(lam (n) (app factorial_plus$lr_N n base))` — the Lam's free var
|
|
; `base` becomes a closure-env capture under the standard 8b ABI.
|
|
; This exercises the dynamic-env path (lifted fn has extra params,
|
|
; the eta-Lam captures them).
|
|
;
|
|
; Expected stdout (one per line):
|
|
; apply5(factorial_plus[base=10]) = 5*4*3*2*(1+10) = 1320
|
|
; apply5(factorial_plus[base=100]) = 5*4*3*2*(1+100) = 12120
|
|
|
|
(module local_rec_as_value_capture
|
|
|
|
(fn apply5
|
|
(doc "Higher-order: applies its fn argument to 5.")
|
|
(type (fn-type (params (fn-type (params (con Int)) (ret (con Int)))) (ret (con Int))))
|
|
(params f)
|
|
(body (app f 5)))
|
|
|
|
(fn run_with_base
|
|
(doc "Build a recursive helper that captures `base` and pass it as a value to apply5.")
|
|
(type (fn-type (params (con Int)) (ret (con Int))))
|
|
(params base)
|
|
(body
|
|
(let-rec factorial_plus
|
|
(params n)
|
|
(type (fn-type (params (con Int)) (ret (con Int))))
|
|
(body
|
|
(if (app <= n 1)
|
|
(app + 1 base)
|
|
(app * n (app factorial_plus (app - n 1)))))
|
|
(in (app apply5 factorial_plus)))))
|
|
|
|
(fn main
|
|
(doc "Iter 16b.5: pass a capturing let-rec helper as a value. Expected stdout: 1320, 12120.")
|
|
(type (fn-type (params) (ret (con Unit)) (effects IO)))
|
|
(params)
|
|
(body
|
|
(seq (do io/print_int (app run_with_base 10))
|
|
(do io/print_int (app run_with_base 100))))))
|