Skip to content

gen-zig: skip dead base-types import; test asserts panic instead of compileError - #1929

Merged
gHashTag merged 1 commit into
masterfrom
fix/zig-dead-import
Aug 8, 2026
Merged

gen-zig: skip dead base-types import; test asserts panic instead of compileError#1929
gHashTag merged 1 commit into
masterfrom
fix/zig-dead-import

Conversation

@gHashTag

@gHashTag gHashTag commented Aug 8, 2026

Copy link
Copy Markdown
Owner

Unlocks the zig test EXECUTION level over tri-net's committed gens (a level above ast-check). Two fixes: (1) use base::types emitted an @import of a never-shipped types.zig even with ZERO references -- every generated file failed with FileNotFound before a single test ran; the import now emits only when the module body references it. (2) Test asserts emitted @compileError, which fires whenever a runtime-condition branch is ANALYZED -- @panic(msg) is the honest runtime failure and still dies at comptime when the condition folds false.

tri-net sweep: 4/69 -> 37/69 gens compile AND pass their test blocks. The remaining 32 are REAL findings the execution level exists to catch (the t27 saturation idiom sum = a + b; if (sum < a) is Zig-fatal at the checked + -- needs +%; genuine runtime test failures like etx's dead-link case; two emission tails) -- tracked in #1928, ratcheting in tri-net. Unit suite 1537/1537; FROZEN_HASH resealed; NOW files updated.

Refs #1928

🤖 Generated with Claude Code

…ompileError

Two fixes unlocking the zig-test EXECUTION level over tri-net's gens:
'use base::types' emitted an @import of a never-shipped types.zig even
with zero references, failing every file before a single test ran (the
import now emits only when referenced); and test asserts used
@CompileError, which fires whenever a runtime-condition branch is
analyzed -- @Panic(msg) is the honest runtime failure and still dies at
comptime when the condition folds false. tri-net sweep: 4/69 -> 37/69
files compile AND pass their test blocks; the rest are REAL findings
(the t27 saturation idiom needs +%, genuine runtime failures, two small
tails) tracked in the issue. Unit suite 1537/1537; FROZEN_HASH resealed.

Refs #1928

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) August 8, 2026 10:11
@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-08 10:12:00 UTC

Summary

Status Count
Total Open PRs 14
PRs with Failing Checks 1
PRs with All Checks Green 13
READY 5
FAILING 1
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=d5c34a630ff9 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 59412fe into master Aug 8, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant