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.
49 lines
1.5 KiB
Plaintext
49 lines
1.5 KiB
Plaintext
; Bench fixture: pure-compute integer loop, no heap.
|
|
;
|
|
; Tail-recursive accumulator loop. Each step does one multiply and one
|
|
; add; no heap allocation, no closure capture, no pattern matching.
|
|
; The point is to isolate codegen quality on tight integer loops:
|
|
; under all three allocators the wall-time should be essentially
|
|
; identical (no allocator pressure to differentiate them), so any
|
|
; observed gc/bump/rc delta on this fixture is signal about codegen,
|
|
; not about memory management.
|
|
;
|
|
; Workload: intsum_loop(n, 0) with n iterations, each contributing
|
|
; i * 7 to the accumulator.
|
|
;
|
|
; Closed form: sum_{i=1..N} i * 7 = 7 * N * (N+1) / 2
|
|
; N = 1_000_000 -> 3_500_003_500_000
|
|
; N = 10_000_000 -> 350_000_035_000_000
|
|
; N = 50_000_000 -> 8_750_000_175_000_000
|
|
;
|
|
; All three results fit comfortably in i64 (max 9.22e18).
|
|
|
|
(module bench_compute_intsum
|
|
|
|
(fn intsum_loop
|
|
(doc "Tail-recursive: acc += i*7 for i in [n, n-1, ..., 1]. Returns final acc.")
|
|
(type
|
|
(fn-type
|
|
(params (con Int) (con Int))
|
|
(ret (con Int))))
|
|
(params i acc)
|
|
(body
|
|
(if (app == i 0)
|
|
acc
|
|
(tail-app intsum_loop
|
|
(app - i 1)
|
|
(app + acc (app * i 7))))))
|
|
|
|
(fn run_one
|
|
(type (fn-type (params (con Int)) (ret (con Unit)) (effects IO)))
|
|
(params n)
|
|
(body (do io/print_int (app intsum_loop n 0))))
|
|
|
|
(fn main
|
|
(type (fn-type (params) (ret (con Unit)) (effects IO)))
|
|
(params)
|
|
(body
|
|
(seq (app run_one 1000000)
|
|
(seq (app run_one 10000000)
|
|
(app run_one 50000000))))))
|