- rawbuf_1_score_table / rawbuf_2_running_max: the header OUTCOME blocks
described the pre-fix breakage (does-not-check / unknown-variable).
Those defects are fixed (B1 #46, B2 #47, B5); update the comments to
the current state — both check, build, run to their expected values
and are leak-clean under AILANG_RC_STATS. The files now serve as
positive regression examples, not bug repros.
- design/models/0007 §RawBuf: ratify the fieldtest's B4 spec_gap. The
`own -> own` signature of RawBuf.set is a threading discipline, not
runtime-enforced single-use; a double-consume of the same owned buffer
aliases one slab (consistent with every owned value in the language).
State that single-use is the author's responsibility and full linear
enforcement is Issue #22 territory.
Surfaced by the raw-buf fieldtest (docs/specs/0058).
Downstream field test of the raw-buf surface as a consumer with only
the public interface (design ledger + `ail` CLI; no crate source).
Four fixtures under examples/fieldtest/, spec at
docs/specs/0058-fieldtest-raw-buf.md. Every recorded outcome
reproduced independently before commit.
Findings (3 bug, 1 spec_gap, 2 working):
- B1 [bug] `borrow (RawBuf a)` receiver is unusable. A fn taking
`borrow (RawBuf Int)` that calls RawBuf.get/.size on the parameter
even once is rejected `consume-while-borrowed` — the diagnostic
names the wrong cause (the receiver is not consumed). The ledger
advertises get/size as borrow-receiver ops, so the documented use
is unreachable from any helper-function decomposition. This blocks
Series (#8) — the milestone's own downstream raison d'être —
whose at/total_count read through a `borrow (Series a)`.
- B2 [bug] An owned RawBuf threaded through a `loop` binder passes
check but panics codegen `unknown variable: b` at build. A plain
Int loop binder builds fine, so the fault is specific to an owned
RawBuf loop binder. Breaks the check↔codegen agreement.
- B3 [bug] `param-not-in-restricted-set` omits the allowed set.
design/models/0007 §4 promises the diagnostic "names the offending
type and the allowed set"; the shipped message names the type, the
type-var, and the home type but not `{Int, Float, Bool}`. A
downstream author is told what is wrong but not what is right.
- B4 [spec_gap] RawBuf.set receiver double-consume is not enforced;
two set calls on the same owned buffer silently alias the slab.
Not raw-buf-specific (owned Str/ADT behave identically) — a
pre-existing linearity-non-enforcement property. Recorded because
RawBuf's own→own mutation is the first place a silent alias yields
a mutated-in-place surprise. Ratify in the ledger or open a backlog
item for full linear enforcement.
- W1 [working] `(new …)` sugar + inference-from-use across
Int/Float/Bool builds and runs first try (sensor_pair prints 5.0);
the Bool i1/i8 packing edge round-trips. The milestone's cleanest win.
- W2 [working] param-in reject fires for both Str and a user TypeDef.
Net: B1+B2 mean the only RawBuf programs that build today are
straight-line owned let-threading with literal indices — the
shipped-fixture shape. Helper decomposition (B1) and runtime-length
loop fill (B2) both fail. fieldtest does not self-resolve; routing
is the orchestrator's call.
Brummel