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.
27 lines
953 B
Plaintext
27 lines
953 B
Plaintext
; Iter 18c.1 — `(clone X)` schema floor.
|
|
;
|
|
; The `clone` form is an additive `Term` variant. In 18c.1 it is
|
|
; identity for both the typechecker and the codegen — `(clone X)`
|
|
; has the same type as `X` and lowers to the same SSA reg with no
|
|
; extra IR. Iter 18c.3 will replace the codegen passthrough with
|
|
; `call void @ailang_rc_inc(ptr %v)` under `--alloc=rc`; for now
|
|
; the wrapper's only role is to record author intent.
|
|
;
|
|
; This fixture wraps a let-bound `Int` in `(clone x)` at its single
|
|
; use site. The inner term is a primitive value (Int) so RC inc is
|
|
; meaningless even in 18c.3 — the point is purely that the schema
|
|
; round-trips and the binary still produces the expected `42`.
|
|
;
|
|
; Expected stdout:
|
|
; 42
|
|
|
|
(module clone_demo
|
|
|
|
(fn main
|
|
(doc "Use `(clone x)` on a let-bound Int; print it.")
|
|
(type (fn-type (params) (ret (con Unit)) (effects IO)))
|
|
(params)
|
|
(body
|
|
(let x 42
|
|
(do io/print_int (clone x))))))
|