Brummel
26fb3459d8
The runtime print path now writes exactly the bytes of its
argument with no implicit trailing newline. `io/print_str` is
byte-faithful; authors who want a newline emit `(do io/print_str
"\n")` themselves.
## Codegen
`crates/ailang-codegen/src/lib.rs`:
- Module preamble: `@puts(ptr)` → `@fputs(ptr, ptr)` plus
`@stdout = external global ptr` (libc's `FILE *stdout`).
- Effect-op lowering for `io/print_str`: emit
`getelementptr +8` then `load ptr, ptr @stdout` then
`call/tail call i32 @fputs(ptr bytes, ptr fp)`. Identical
bytes-pointer GEP, distinct sink.
- The pinned IR-shape test renames from
`print_str_calls_puts_with_bytes_pointer` to
`print_str_calls_fputs_with_bytes_pointer_and_stdout` and now
asserts: bytes-GEP present, stdout-load present, both module-
preamble declarations present, and no `@puts(` call anywhere
in the emitted IR.
## Why this shape, and not the alternatives
- *Rename `io/print_str` to `io/println_str` (issue #29 option 2)*
— kept the auto-newline, just relabelled it. AILang's design
bias is explicit-over-implicit (CLAUDE.md: implicit conversions
cut). Auto-newline is a hidden runtime augmentation; the rename
would have preserved it. Rejected.
- *Append `\n` inside the polymorphic `print` (Show-mediated)
function in `examples/prelude.ail`* — would have been a one-line
fix. Rejected: `print` is the Show-mediated formatter, not a
newline emitter; baking a newline into it would have re-imposed
the same implicit-augmentation problem one layer up, breaking
callers that legitimately want pure-bytes output.
## Fixture / test sweep
30 `.ail` fixtures whose owning tests asserted line-separated
stdout now emit explicit `(do io/print_str "\n")` after each
print. Tests that asserted on multi-line stdout (`show_print_e2e`,
`floats_e2e`, `str_concat_e2e`, `eq_ord_e2e`, several `print_*`
smoke tests) had their fixtures sweetened the same way; assertions
themselves remain the canonical observable output. Fixtures that
never relied on the newline (no test ever read the absence of one)
were left untouched.
## Migrated metadata
- `crates/ailang-core/tests/hash_pin.rs`: the `ordering_match::main`
canonical hash is refreshed (`b65a7f834703ffb4` →
`8ed47b4062ce00f5`). The comment now names both successive
corpus migrations honestly: the per-type-print-retirement (which
moved `(do io/print_int x)` to `(app print x)`) AND this
fputs swap (which wrapped that with `(seq ... (do io/print_str
"\n"))`).
- `design/contracts/str-abi.md`: the consumer-ABI table now lists
`@fputs` as the print sink. A prose paragraph documents the
byte-faithful semantics and references this issue.
- `examples/ordering_match.prose.txt`: regenerated from the
updated `ordering_match.ail`.
- `crates/ail/tests/snapshots/{hello,sum,max3,list,ws_main}.ll`:
IR snapshots regenerated via `UPDATE_SNAPSHOTS=1`.
- Stale `@puts` comments in `runtime/str.c`,
`crates/ail/tests/{e2e,show_print_e2e,print_no_leak_pin}.rs`
replaced with `@fputs`.
## Verification
- `cargo test -p ail --test print_str_no_auto_newline_e2e` — both
RED tests from commit c8ecfa3 now pass.
- `cargo test --workspace` — 90 test groups GREEN, 0 failures.
- `cargo build --workspace` — GREEN.
- No new clippy lints (24 warnings pre-existing in
`crates/ailang-core/src/lib.rs:129`).
- Stats: `bench/orchestrator-stats/2026-05-21-iter-bugfix-print-
str-fputs.json` — 1/1 tasks, 0 re-loops, 0 review loops.
## Empirical evidence cited
Caught in the 2026-05-21 Qwen3-Coder naming-A/B run
(`experiments/2026-05-21-naming-ab/runs/r1/`): every cohort wrote
`(do io/print_str "...\n")` with explicit `\n` and got doubled
newlines, failing the `t3_main_prints` stdout match across all
three cohorts. The empirical LLM-natural form already assumes the
new (post-this-commit) semantics — confirming the
feature-acceptance test in CLAUDE.md.
closes #29
54 lines
1.9 KiB
Plaintext
54 lines
1.9 KiB
Plaintext
; Iter 16b.7 — nested LetRec mutual capture (params, not name).
|
|
;
|
|
; `nested_sum(n)` returns the sum 1 + 2 + ... + n by combining two
|
|
; recursive helpers. The OUTER let-rec `outer(i)` iterates i over
|
|
; 1..=n; for each i it calls the INNER let-rec `inner(j)` to count
|
|
; how many integers are in 1..=i (= i). The total is then
|
|
; 1 + 2 + ... + n = n*(n+1)/2.
|
|
;
|
|
; The shape exercises:
|
|
; - outer captures `n` from `nested_sum`'s fn-params (16b.2 case).
|
|
; - inner captures `i` from outer LetRec's PARAMS (16b.7 case
|
|
; under iter — outer LetRec's params are KnownType in body
|
|
; scope, so the inner lift sees a resolvable capture type).
|
|
; - inner does NOT capture outer's NAME (still rejected in 16b.7).
|
|
;
|
|
; Expected stdout (one per line):
|
|
; nested_sum(1) = 1
|
|
; nested_sum(3) = 6
|
|
; nested_sum(5) = 15
|
|
|
|
(module nested_let_rec
|
|
|
|
(fn nested_sum
|
|
(doc "Sum 1 + 2 + ... + n by nested LetRec helpers; inner captures outer's param i.")
|
|
(type (fn-type (params (con Int)) (ret (con Int))))
|
|
(params n)
|
|
(body
|
|
(let-rec outer
|
|
(params i)
|
|
(type (fn-type (params (con Int)) (ret (con Int))))
|
|
(body
|
|
(if (app gt i n)
|
|
0
|
|
(app +
|
|
(let-rec inner
|
|
(params j)
|
|
(type (fn-type (params (con Int)) (ret (con Int))))
|
|
(body
|
|
(if (app gt j i)
|
|
0
|
|
(app + 1 (app inner (app + j 1)))))
|
|
(in (app inner 1)))
|
|
(app outer (app + i 1)))))
|
|
(in (app outer 1)))))
|
|
|
|
(fn main
|
|
(doc "Drive nested_sum at 1, 3, 5. Expected (per line): 1, 6, 15.")
|
|
(type (fn-type (params) (ret (con Unit)) (effects IO)))
|
|
(params)
|
|
(body
|
|
(seq (seq (app print (app nested_sum 1)) (do io/print_str "\n"))
|
|
(seq (seq (app print (app nested_sum 3)) (do io/print_str "\n"))
|
|
(seq (app print (app nested_sum 5)) (do io/print_str "\n")))))))
|