Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 19, 2026
Merged
Merged
Merged
This was referenced Oct 19, 2026
Merged
Merged
Merged
Merged
12 tasks
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.
Closes #10860. Part of epic #10863. Stacked on #10874 (
t27b watch); retargets to master after it lands.t27b buildwrites<out>.buildnext to the object and skips the next build when nothing that feeds the object changed.--forcebuilds anyway.Where the decisions live
specs/tri/t27b/build_record.t27(new): which parts a native object has (root spec,useclosure, thet27bbinary, the byte-changing flags), the reason words,--force, rewrite only on different bytes, write a record only after a successful build. The reuse rule itself isspecs/verified/reuse.t27throughuse: MISSING never counts as SAME, the reason is the first part that differs. 8/8 tests undert27c test-report, 0 vacuous.gen/rust/tri/t27b/build_record.rs:t27c gen-rustoutput (sha256 697e3671...35c4).cli/t27b/src/main.rs: thin glue. The record issha256sumformat (#lines for the head and flags), hashed and checked by the system sha256 tool (sha256sum, elseshasum -a 256).cmd_buildandwatchleave the object untouched when the new bytes are identical, so a hot-reloading app does not restart on a comment edit. This PR's own diff in the file is 40 added / 41 removed: four multi-line arg parsers became one-liners and ten comment lines that restatedspecs/tri/t27b/usage.t27were dropped.specs/tri/t27b/usage.t27+gen/rust/tri/t27b/usage.rs:--forceint27b help.docs/reports/t27b_expectations.json: build_record.t27 listed for the ratchet.Measured on the Railway lab
t27b build specs/tri/t27b/watch_build.t27 -o /tmp/br/wb.o --elf --time:no-record, record of 16 lines (head, flags, 13 closure files, the binary);reuse, 17 ms wall, no front end run;--machothen--elf:flags-changedboth times;spec-changed, rebuilt, object sha256 5f6cb42f...325c unchanged and its mtime unchanged (0 rewrites);specs/verified/reuse.t27):closure-changed;--force:forced.🤖 Generated with Claude Code