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.
34 lines
1.3 KiB
Plaintext
34 lines
1.3 KiB
Plaintext
; Iter 16b.5 — LetRec name as value (in_term, no capture).
|
|
; A recursive `factorial` is bound by `(let-rec ...)` inside `main`,
|
|
; then in the in-clause it is passed as a VALUE to a higher-order
|
|
; combinator `apply5` (which expects `Fn(Int) -> Int`). Without
|
|
; 16b.5, the desugar pass would panic with the "name-as-value not
|
|
; supported" message. With 16b.5 it wraps the in-term in
|
|
; `(let factorial (lam ...) ...)` whose lam eta-expands the lifted
|
|
; top-level fn — so `factorial` reaches `apply5` as a closure-pair
|
|
; value just like any other fn-value (Iter 7/8b ABI).
|
|
;
|
|
; Expected stdout: 120 (= apply5 factorial = factorial 5).
|
|
|
|
(module local_rec_as_value
|
|
|
|
(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 main
|
|
(doc "Iter 16b.5: pass a let-rec'd factorial as a value to apply5. Expected stdout: 120.")
|
|
(type (fn-type (params) (ret (con Unit)) (effects IO)))
|
|
(params)
|
|
(body
|
|
(let-rec factorial
|
|
(params n)
|
|
(type (fn-type (params (con Int)) (ret (con Int))))
|
|
(body
|
|
(if (app <= n 1)
|
|
1
|
|
(app * n (app factorial (app - n 1)))))
|
|
(in (do io/print_int (app apply5 factorial)))))))
|