AILang

Author SHA1 Message Date

Author	SHA1	Message	Date
Brummel	9fdc4cacff	iter form-a.1 (Tasks 6-12): milestone close Second half of the form-a-default-authoring milestone-close iter (Boss-decided strategy C, big-bang). All seven tasks DONE; cargo test --workspace green at every per-task boundary. T6 — Bench-driver suffix flip from .ail.json to .ail across 4 Python scripts + run.sh. compile_check.py + cross_lang.py exit 0. T7 — Re-author e2e.rs raw-JSON-inspect tests: - diff_detects_changed_def — derive sum.ail.json on-the-fly via `ail parse examples/sum.ail` into tempdir, then mutate + diff. - borrow_own_demo_modes_are_metadata_only — same pattern. - reuse_as_demo_under_rc_uses_inplace_rewrite — same pattern. - render_parse_round_trip_canonical — RETIRED (subsumed by T1's cli_parse_then_render_then_parse_is_idempotent over whole corpus). - ail_run_accepts_ail_source_with_same_stdout_as_ail_json — re-authored to derive hello.ail.json in a per-process tempdir from hello.ail via `ail parse`, then assert dual-form stdout. T8 — Bulk-delete 156 non-carve-out .ail.json. Inventory: 8 .ail.json (carve-outs, alphabetical: broken_unbound + prelude + 3× test_22b2_* + 3× test_ct1_*) + 157 .ail. carve_out_inventory test un-#[ignore]'d and green. Forward-pulled 20 repairs that the T1-5 dispatch's recon missed (12 Group-B suffix + 5 Group-A load_workspace + 3 ail_run sites). Also forward-pulled T9 Step 5 (schema_coverage corpus flip from .ail.json to .ail) to satisfy T8's green-gate. T9 — Retire obsolete roundtrip tests: - print_then_parse_round_trips_every_fixture (round_trip.rs) - every_ail_fixture_matches_its_json_counterpart (round_trip.rs) - cli_render_then_parse_preserves_canonical_bytes_on_every_fixture - Dead helpers: list_json_fixtures ×2, round_trip_one, strip_trailing_newlines. Schema-coverage corpus already flipped in T8 (forward-pull). T10 — DESIGN.md §"Roundtrip Invariant" (lines 2027-2109) restated with parse-determinism + idempotency + CLI-pipeline-idempotency + carve-out-anchor framing. Five surviving enforcement tests named. §"Float literals" and §"Why anchored at top level" preserved. T11 — §A4 doctrine edits: CLAUDE.md:5-6 + DESIGN.md:465-466. Canonical form remains JSON-AST; authoring projection is .ail; build derives JSON-AST in-process via ailang_surface::parse. T12 — Milestone close: - WhatsNew entry: user-facing language, lead with the change. - Roadmap: [milestone] form-a struck [x] with closing note. - Final inventory verified: 8 .ail.json + 157 .ail. - Final cargo test --workspace: 557 passed, 0 failed, 3 ignored. - bench/compile_check.py + bench/cross_lang.py: exit 0. Test math: pre-iter 558 baseline + 3 new T1 tests = 561, − 1 (T7 retire) − 3 (T9 retire) = 557 final. INDEX.md appended with the full iter summary covering T1-T12 (the T1-5 commit at `77b28ad` deferred the INDEX line to full-iter close). Milestone [Form-A as the default authoring surface] structurally closed. The compile-time-embed carve-out (prelude.ail.json) is the subject of the queued follow-up milestone [Prelude embed: Form-A as compile-time source]. audit-form-a runs as the next dispatch.	2026-05-13 11:31:39 +02:00
Brummel	aea3758742	tidy: 21'g — resolve drift after 21'-arc close Three drift items from ailang-architect, plus one false-positive surfaced during verification: 1. DESIGN.md silent on closure-pair 4.14x finding (21'b). Decision-10 ratified: "Workload scope of the 1.3x target" paragraph scopes the retirement gate to linear/tree/poly-ADT workloads; closure-pair carve-out documented as representational cost (closure cell + env struct = 2 allocs per step) until a slab/pool answer ships. 2. bench/compile_check.py corpus drift. Three fixtures added (bench_compute_intsum, bench_compute_collatz, bench_list_sum_explicit), re-baselined. Now 12 fixtures x 2 ops = 24 compile-time metrics. 3. baseline.json convention not codified. Note field gains "max-of-distribution gets wider band than percentile" convention discovered in 21'd. 4. (verification finding) bench_compute_intsum cross_lang tolerances at 15%/12% fire on subprocess-spawn jitter for sub-millisecond fixtures. Widened to 35% across all five intsum metrics; convention recorded in baseline_cross_lang note field (sub-ms fixtures need looser bands). All three bench gates re-run sequentially after edits: bench/check.py — 63 metrics; 63 stable bench/compile_check.py — 24 metrics; 24 stable bench/cross_lang.py — 25 metrics; 25 stable Total: 112 metrics under regression coverage, all green. 288 tests passing, 3 ignored. No Rust changes.	2026-05-09 01:40:36 +02:00
Brummel	416d763b73	bench: 21'c — compile-time regression bench (check.py + compile_check.py) Closes the second axis the user named: every typechecker / codegen perf change was previously invisible to the tidy-iter gate. With Family 21 typeclasses (queued) and 21'b's poly-ADT additions both pushing on the typechecker, naive substitution loops would have landed silently and decayed the compile path. bench/compile_check.py is a separate script from bench/check.py because the methodology differs: sub-process spawn timing on small workloads (1ms scale for `ail check`, 65ms for `ail build`) vs. allocator-stress on large ones (multi-second). Tolerances differ by an order of magnitude (25% / 20% here vs. 5-15% there). Empirically: ail check is sub-ms across the corpus, dominated by subprocess spawn (~5-10ms on Linux); ail build is 63-69ms, dominated by clang's link step. The bench is a catastrophe detector (10x slowdowns visible) — finer regressions need a profiler. CLAUDE.md updated to list both scripts as co-equal tidy-iter gates alongside the architect drift report; exit 0/1/2 semantics are uniform across both. JOURNAL queue: 21'd (pure-compute fixtures) and 21'e (cross- language reference / hand-C ratio) remain to land the LLVM- linkable performance claim.	2026-05-09 00:59:00 +02:00

9fdc4cacff

iter form-a.1 (Tasks 6-12): milestone close

Second half of the form-a-default-authoring milestone-close iter
(Boss-decided strategy C, big-bang). All seven tasks DONE; cargo
test --workspace green at every per-task boundary.

T6 — Bench-driver suffix flip from .ail.json to .ail across 4
Python scripts + run.sh. compile_check.py + cross_lang.py exit 0.

T7 — Re-author e2e.rs raw-JSON-inspect tests:
- diff_detects_changed_def — derive sum.ail.json on-the-fly via
  `ail parse examples/sum.ail` into tempdir, then mutate + diff.
- borrow_own_demo_modes_are_metadata_only — same pattern.
- reuse_as_demo_under_rc_uses_inplace_rewrite — same pattern.
- render_parse_round_trip_canonical — RETIRED (subsumed by T1's
  cli_parse_then_render_then_parse_is_idempotent over whole corpus).
- ail_run_accepts_ail_source_with_same_stdout_as_ail_json —
  re-authored to derive hello.ail.json in a per-process tempdir
  from hello.ail via `ail parse`, then assert dual-form stdout.

T8 — Bulk-delete 156 non-carve-out .ail.json. Inventory:
8 .ail.json (carve-outs, alphabetical: broken_unbound + prelude
+ 3× test_22b2_* + 3× test_ct1_*) + 157 .ail. carve_out_inventory
test un-#[ignore]'d and green. Forward-pulled 20 repairs that the
T1-5 dispatch's recon missed (12 Group-B suffix + 5 Group-A
load_workspace + 3 ail_run sites). Also forward-pulled T9 Step 5
(schema_coverage corpus flip from .ail.json to .ail) to satisfy
T8's green-gate.

T9 — Retire obsolete roundtrip tests:
- print_then_parse_round_trips_every_fixture (round_trip.rs)
- every_ail_fixture_matches_its_json_counterpart (round_trip.rs)
- cli_render_then_parse_preserves_canonical_bytes_on_every_fixture
- Dead helpers: list_json_fixtures ×2, round_trip_one,
  strip_trailing_newlines.
Schema-coverage corpus already flipped in T8 (forward-pull).

T10 — DESIGN.md §"Roundtrip Invariant" (lines 2027-2109) restated
with parse-determinism + idempotency + CLI-pipeline-idempotency +
carve-out-anchor framing. Five surviving enforcement tests named.
§"Float literals" and §"Why anchored at top level" preserved.

T11 — §A4 doctrine edits: CLAUDE.md:5-6 + DESIGN.md:465-466.
Canonical form remains JSON-AST; authoring projection is .ail;
build derives JSON-AST in-process via ailang_surface::parse.

T12 — Milestone close:
- WhatsNew entry: user-facing language, lead with the change.
- Roadmap: [milestone] form-a struck [x] with closing note.
- Final inventory verified: 8 .ail.json + 157 .ail.
- Final cargo test --workspace: 557 passed, 0 failed, 3 ignored.
- bench/compile_check.py + bench/cross_lang.py: exit 0.

Test math: pre-iter 558 baseline + 3 new T1 tests = 561, − 1
(T7 retire) − 3 (T9 retire) = 557 final.

INDEX.md appended with the full iter summary covering T1-T12 (the
T1-5 commit at 77b28ad deferred the INDEX line to full-iter close).

Milestone [Form-A as the default authoring surface] structurally
closed. The compile-time-embed carve-out (prelude.ail.json) is
the subject of the queued follow-up milestone [Prelude embed:
Form-A as compile-time source]. audit-form-a runs as the next
dispatch.

2026-05-13 11:31:39 +02:00

Brummel

aea3758742

tidy: 21'g — resolve drift after 21'-arc close

Three drift items from ailang-architect, plus one false-positive
surfaced during verification:

  1. DESIGN.md silent on closure-pair 4.14x finding (21'b).
     Decision-10 ratified: "Workload scope of the 1.3x target"
     paragraph scopes the retirement gate to linear/tree/poly-ADT
     workloads; closure-pair carve-out documented as
     representational cost (closure cell + env struct = 2 allocs
     per step) until a slab/pool answer ships.

  2. bench/compile_check.py corpus drift. Three fixtures added
     (bench_compute_intsum, bench_compute_collatz,
     bench_list_sum_explicit), re-baselined. Now 12 fixtures x
     2 ops = 24 compile-time metrics.

  3. baseline.json convention not codified. Note field gains
     "max-of-distribution gets wider band than percentile"
     convention discovered in 21'd.

  4. (verification finding) bench_compute_intsum cross_lang
     tolerances at 15%/12% fire on subprocess-spawn jitter for
     sub-millisecond fixtures. Widened to 35% across all five
     intsum metrics; convention recorded in baseline_cross_lang
     note field (sub-ms fixtures need looser bands).

All three bench gates re-run sequentially after edits:
  bench/check.py        — 63 metrics; 63 stable
  bench/compile_check.py — 24 metrics; 24 stable
  bench/cross_lang.py    — 25 metrics; 25 stable

Total: 112 metrics under regression coverage, all green.

288 tests passing, 3 ignored. No Rust changes.

2026-05-09 01:40:36 +02:00

Brummel

416d763b73

bench: 21'c — compile-time regression bench (check.py + compile_check.py)

Closes the second axis the user named: every typechecker / codegen
perf change was previously invisible to the tidy-iter gate. With
Family 21 typeclasses (queued) and 21'b's poly-ADT additions both
pushing on the typechecker, naive substitution loops would have
landed silently and decayed the compile path.

bench/compile_check.py is a separate script from bench/check.py
because the methodology differs: sub-process spawn timing on small
workloads (1ms scale for `ail check`, 65ms for `ail build`) vs.
allocator-stress on large ones (multi-second). Tolerances differ
by an order of magnitude (25% / 20% here vs. 5-15% there).

Empirically: ail check is sub-ms across the corpus, dominated by
subprocess spawn (~5-10ms on Linux); ail build is 63-69ms,
dominated by clang's link step. The bench is a catastrophe
detector (10x slowdowns visible) — finer regressions need a
profiler. CLAUDE.md updated to list both scripts as co-equal
tidy-iter gates alongside the architect drift report; exit 0/1/2
semantics are uniform across both.

JOURNAL queue: 21'd (pure-compute fixtures) and 21'e (cross-
language reference / hand-C ratio) remain to land the LLVM-
linkable performance claim.

2026-05-09 00:59:00 +02:00

3 Commits