Brummel
e25580e3a3
Wires the #55-cutover fieldtest into a durable regression net. The
fieldtest exercised the post-cutover ParamMode={Own,Borrow} surface as a
downstream LLM author would and produced 12 fixtures + a report; left as
loose files they would be dead fixtures that drift. This commits them as
a protected property.
crates/ail/tests/cut55_cutover_surface.rs — one table-driven test running
each fixture through `ail check` and asserting accept (exit 0) or reject
at the right pipeline stage. Reject rows key on the bracketed diagnostic
CODE (consume-while-borrowed, borrow-over-value, borrow-return-not-permitted,
surface-parse-error), NOT message text, so the test is decoupled from the
diagnostic-wording improvement tracked separately.
examples/fieldtest/cut55_*.ail — the corpus. cut55_2c is the #58 repro
(now correctly rejected). cut55_2b was misanalysed by the fieldtest as a
consume-while-borrowed reject; in fact bump's recursive param is
(borrow List) so the tail is only borrowed, never consumed into an own
slot — `ail check` correctly accepts it. Renamed to
cut55_2b_borrow_traversal_clean and recast as the #58 false-positive
guard (a borrow-position use of a heap sub-binder must stay accepted).
cut55_1b similarly does not fire over-strict-mode (its recursive call
consumes the tail, so the lint's consume_count==0 premise fails) — comment
corrected; it is a plain accept. cut55_1c is the genuine over-strict-mode
example (accepts exit 0, emits the warning).
docs/specs/0065-eliminate-implicit-mode fieldtest report — moved 2c to
the reject set, added the 2b false-positive-guard section, marked the
double-free spec_gap RESOLVED (it shipped as the #58 fix).
Relates to #55.
34 lines
1.2 KiB
Plaintext
34 lines
1.2 KiB
Plaintext
; Fieldtest cut55-1b — decision (a), over-strict `own` that does NOT trip
|
|
; the lint (boundary case).
|
|
;
|
|
; Same shape as cut55-1 but `xs` is annotated `(own (con List))`. One might
|
|
; expect the `over-strict-mode` lint to fire (xs is only read at the top
|
|
; level). It does NOT: the Cons arm recurses via `(app length t)`, and
|
|
; `length`'s own self-param is `(own ...)`, so passing the heap tail `t`
|
|
; into it counts as a consume. The lint's premise (consume_count == 0) is
|
|
; therefore false, and no warning is emitted. The fixture still legitimately
|
|
; ACCEPTs (an over-strict but sound annotation is allowed). cut55_1c is the
|
|
; sibling where the lint DOES fire (a true read-only with no recursive
|
|
; consume).
|
|
;
|
|
; Expected: ail check -> ok, exit 0 (no over-strict-mode warning).
|
|
|
|
(module cut55_1b_overstrict_own
|
|
|
|
(data List
|
|
(ctor Nil)
|
|
(ctor Cons (con Int) (con List)))
|
|
|
|
(fn length
|
|
(doc "Annotated own but only reads xs — should be flagged over-strict.")
|
|
(type
|
|
(fn-type
|
|
(params (own (con List)))
|
|
(ret (own (con Int)))))
|
|
(params xs)
|
|
(body
|
|
(match xs
|
|
(case (pat-ctor Nil) 0)
|
|
(case (pat-ctor Cons h t)
|
|
(app + 1 (app length t)))))))
|