Repository navigation
Description
Boundary
This decides the T730 test-report ACCOUNTING for comptime-folded asserts only. In scope: how t27c test-report reports a test whose asserts all folded at comptime (today: Some(0) + the VACUOUS label), and whether the language gains a runtime-forcing assert form. Out of scope: the counting mechanism itself (#5980 records it -- __t27_tally works as designed), the wasm floor-13 landing (#12711/#12748, done), and any change to what assert means in running code.
Evidence (probes on t27c 0.5.2, recorded on #5980): a module-const array index folds at comptime -- pub const V: [2]u32 = [55, 14]; assert(V[1] == 14) passes with 0 runtime asserts and is labeled VACUOUS, while the same assert over a local array executes 1 runtime assert. The plain zig is correct and would fail loudly if the constant changed; the runtime counter just cannot see a comptime check.
User scenarios
- An epic-progress card wants to pin constants in its own data (
assert(DATE[1] == 20261027)). Today the author writes accessor functions that force a runtime read -- a workaround pattern that exists in at least one landed spec and is undocumented. - A spec author writes a const-checking test directly, sees PASS with the VACUOUS flag, and reads it as 'my test certified nothing' -- when it actually verified at compile time.
- A reviewer reads a test report with vacuous passes and cannot tell 'trivial backend' from 'compile-time verified' from 'author forgot the body'.
Requirements
Any chosen path must keep T730's honest accounting (a pass never claims more verification than executed) and must not inflate runtime-assert counts with comptime-only checks. The options:
- (a) report state: test-report gains COMPTIME-VERIFIED as a distinct outcome for a passing test whose asserts all folded (the tally site already knows foldedness); the VACUOUS label then means only 'truly trivial'. Smallest: test_report.rs + report format + the COUNTER shim stays.
- (b) language form: a runtime-forcing assert (or an attribute) that inhibits comptime folding, so const-data checks count as runtime asserts. Larger: touches the emit on every backend.
- (c) documented idiom: keep the behavior, document the accessor pattern as the idiom for runtime checks over const data, and teach VACUOUS readers to check for comptime folding. Smallest of all, but every future author re-discovers the fold.
Success criteria
- The probe pair from epic: self-host t27c -- rewrite the compiler from Rust into t27 #5980 (local array = 1 runtime assert; const array = folded) becomes an acceptance test for whichever path lands.
- A spec author in scenario 2 can tell from the report alone what kind of verification happened.
- The epic-progress card (epic: merge-train and repo hygiene -- the queue, the branches, the CI queue ceiling #12660 family) tests its own const data without accessor indirection, if (a) or (b).
- No regression: the 2227-spec corpus report's pass/vacuous counts change only by reclassification, never by silent re-run differences.
Recommendation: (a) first (it unblocks scenario 2 immediately and makes 3 legible), (c) shipped alongside as documentation, (b) deferred until a real workload needs runtime checks over const data. Refs: #5980 (the five-probe investigation), #12714 (the accessor workaround shipped in a landed spec), #12719 (the epic card that hit this).
Activity
github-actions commentedon Oct 26, 2026
Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.
exit 0, or a backticked commandreport: a folded check is CT-VERIFIED, not VACUOUS -- T730's accounti…
report: a folded check is CT-VERIFIED, not VACUOUS -- T730's accounti…
t27b: the interpreter counts folded checks as ct_verified -- the CT-V…
lab: the pass_ct reader -- the corpus aggregates count the compile-ti…
t27b: pass_ct -- the verdict layer carries the CT-VERIFIED count (sta…
lab: the pass_ct reader -- the corpus aggregates count the compile-ti…
hosting: pass_ct joins the verdict vocabulary -- row.t27 words, the s…
policy: the budget discipline card -- the session's refusals replayed…
t27os: the graph plane -- the tap ring folded into per-kind rows and …
t27os: the graph plane -- the tap ring folded into per-kind rows and …
t27os: the LIVE MYCELIUM band on the Queen screen -- the swarm's grap…
fix(t27b): regenerate steward.c so is_pass knows pass_ct; the ledger …