Skip to content

fix ci after #11: rustfmt rewraps in the round-4 test code - #12

Merged
marcuspat merged 1 commit into
mainfrom
fix/ci-fmt
Oct 4, 2026
Merged

marcuspat merged 1 commit into
mainfrom
fix/ci-fmt

Conversation

@marcuspat

Copy link
Copy Markdown
Owner

Four pure-formatting hunks from the #11 merge that CI caught (rustc is broken on the authoring Mac, so rustfmt never ran locally): the traversal-assert chain, the jt/jf tuple loop, the jump-count assert, and two golden-target asserts — exactly the forms rustfmt wants, zero semantic change.

Four formatting hunks CI caught (rustc is broken on the authoring
Mac): the traversal assert chain, the jt/jf tuple loop, the
jump-count assert, and the two golden-target asserts - exactly the
forms rustfmt wants, no semantic change.
@marcuspat

Copy link
Copy Markdown
Owner Author

Gate review — reviewer: claude

Lanes: reviewed by claude

GATE USAGE reviewer=claude in=2 cached=39,201 out=235 6s model=claude-haiku-4-5-20251001,claude-opus-5[1m] $0.279 API-equiv (not billed on subscription)

Diff is pure rustfmt rewrapping of test code — two line-breaks in filesystem.rs:565, and in sandbox.rs the for (name, target) in [...] array/brace split (819), the assert!(jumps >= 5, ...) wrap (830), and the two assert_eq! wraps (838, 843). No token sequence changes: same jump-target arithmetic, same comparands (13, 11), same assertion predicates and messages. Nothing added, removed, or weakened — the bounds loop still iterates both jt/jf, and the jumps >= 5 guard that keeps the walk from vacuously passing is intact.

VERDICT: APPROVED


VERDICT: APPROVED

@marcuspat
marcuspat merged commit bb69801 into main Oct 4, 2026
3 of 5 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