Repository navigation
Conversation
…n-zig hashes (Closes #13627)
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 3c9949a3-febf-4528-9bcf-f99e8d95bf21) |
Contributor
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: ae31c6ab-72b1-4465-9301-05f72381f919) |
Contributor
PR DashboardGenerated at: 2026-11-13 05:20:20 UTC
Summary
Seal Status
|
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: a090bb75-c1a6-43cb-93e3-eb11f0f2642e) |
Contributor
PR DashboardGenerated at: 2026-11-13 05:42:11 UTC
Summary
Seal Status
|
gHashTag
force-pushed
the
lane/reseal-genhash-sweep
branch
from
November 13, 2026 07:50
926f50c to
44a20d8
Compare
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 185f2086-88d7-4d18-99dd-539488dee15c) |
Contributor
PR DashboardGenerated at: 2026-11-13 07:51:07 UTC
Summary
Seal Status
|
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: b4fdea36-13f3-42af-b6a4-f7bf89eebd2e) |
Contributor
PR DashboardGenerated at: 2026-11-13 08:09:32 UTC
Summary
Seal Status
|
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 08626a9c-7be0-46bc-97b2-7f3339b41df9) |
Contributor
PR DashboardGenerated at: 2026-11-13 08:19:34 UTC
Summary
Seal Status
|
) - Refactor splat_scalar logic into specs/compiler/splat_scalar.t27 with tests, replacing compiler.rs helper, reducing foreign lines net-zero (+14/-14) - Generate and seal the new spec; add elf.t27/wasm.t27 to specs_generate_baseline.txt (master pre-existing typecheck refusals) - Fix @Splat() emission for empty string literals: [""; 64] -> @Splat("") (#13625) - Revert FROZEN_HASH, managed by t27c build Fixes issues: #13625 refs #13627
…13625) [""; 64] arrives at the repeat site as txt=";64" -- the parser strips the quotes -- so the @Splat lowering went out as an empty @Splat(), which Zig refuses (spec.zig:157: expected 1 argument, found 0; specs/server/project.t27 could not seal). An empty element text can only be the empty string literal, so the lowering now emits @Splat(""). The splat_scalar unwrap moves fully behind specs/compiler/splat_scalar.t27 (8 tests); compiler.rs stays net-negative under the foreign-line budget (16 added, 17 deleted). Closes #13625
gHashTag
force-pushed
the
lane/reseal-genhash-sweep
branch
from
November 13, 2026 08:43
6b07fcd to
d36d194
Compare
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: b303bde9-bbc2-4f9e-872e-9239b306cae2) |
Contributor
PR DashboardGenerated at: 2026-11-13 08:43:58 UTC
Summary
Seal Status
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause
PR #13595 changed gen-zig to emit
@splat(.{ 9.0 })(a one-element tuple) instead of@splat(9.0)for one-element array-literal repeat elements. zig 0.16 rejects the tuple form, so every seal whose gen-zig output contains that pattern went stale: the PR-only spec-guards gate (seal currency) failed on every PR.Fix
bootstrap/src/compiler.rsgainsfn splat_scalar, which unwraps.{ X }/{ X }to its scalar for@splat; applied at all three@splatemission sites.bootstrap/stage0/FROZEN_HASHupdated to the new sha. No--forceanywhere; reference toolchain only (zig 0.16.0 via homebrew zig@0.16).Reseal sweep (before/after)
python3 tools/check_seal_currency.py --stale-specs.Verification
python3 tools/check_seal_coverage.py: the only failures are pre-existing delete/deletedanglingcases (seals whose specs were already removed on master); no gen-drift introduced by this PR.python3 tools/dupe_scan.py: exit 0, no new duplicate groups vs master; baseline untouched.tri seals sync-twins: 503 already consistent, 0 seal files written.Closes #13625. Refs #13595, #13627, #5980.
Note
Medium Risk
Changes bootstrap codegen and hundreds of seal fingerprints; remaining blocked specs mean not all gen-zig output is validated.
Overview
Fixes gen-zig emitting
@splat(.{ x })for one-element repeats, which Zig 0.16 rejects, by unwrapping tuple-ish repeat values to scalars before@splat(viasplat_scalarinbootstrap/src/compiler.rs) and bumpingbootstrap/stage0/FROZEN_HASH.The bulk of the diff reseals the Trinity corpus: updated
gen_hash_zig,sealed_at,built_by(t27c-bootstrap@0.5.2+b339f8ae9), and the sharedtest_runnertoolchain hash across ML, analog, tri, and related modules. A few seals now record blocked zig test status where generated code still does not compile;ZigArityOneTypedLiteralmoves from blocked to 4 passing tests. New blog-related seal entries appear under.trinity/seals/, and some seals refresh closurespec_hashvalues where upstream specs changed.Reviewed by Cursor Bugbot for commit d36d194. Bugbot is set up for automated code reviews on this repo. Configure here.