rust: re-bless macro calls against engine main (gitgalaxy#3643) - #157
Merged
Merged
Conversation
A macro invocation is a call to its name (calls_out contract C3). Engine main's CALLS_OUT_RUST now sees `name!(`, so: - a.rs probe_test: calls_out_to [] -> [assert, assert_eq] - b.rs probe_telemetry: calls_out_to [] -> [info, error] docs/calls_out_truth.json: the rust `macros` known gap is closed; the four macro calls join `periphery` (read from a.rs:13-14, b.rs:13-14), and the gap's other sentence (a::probe_globals is a real cross-file edge) moves to `note`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GCpfMCUMpco98QGbsuv2sr
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.
Summary
This is the re-bless owed by squid-protocol/gitgalaxy#3726 (fixes squid-protocol/gitgalaxy#3643), which carried
rosetta:rebless-owed. Under calls_out contract C3, a macro invocation is a call to its name. Engine main's newCALLS_OUT_RUSTnow capturesname!(, so two Rust cells move:a.rs→probe_test[]["assert", "assert_eq"]b.rs→probe_telemetry[]["info", "error"]These are exactly the calls
docs/calls_out_truth.jsonlisted as Rust'smacrosknown gap. Socalls_out_truth.jsonchanges too:macrosknown gap is closed.peripheryforprobe_testandprobe_telemetry. I read them from the source (a.rs:13-14,b.rs:13-14), not from engine output.a::probe_globals(...)is a real cross-file edge") isn't about macros, so it moves tonoterather than being lost.The manifest's
notesgets a dated entry. No ledger entry changes.Tool note:
tools/rebless.pyrefused to write because its round-trip check expectsensure_ascii=False.data/rust/expected_signals.json, like most manifests, is written escaped, with—. I applied the same two cells by hand in the file's own format (indent=2,ensure_ascii=True, trailing newline), so the diff contains only the moved cells and the note.rebless.py's format check is out of step with the corpus for about 29 manifests. That's a separate fix.Cross-repo
verify.ymlchecks out engine main, so this is green by construction.bias-history.ymlregenerates the bias report, and the "corpus owes a re-bless" issue should drop Rust.Verification (against engine main
a285b90f)🤖 Generated with Claude Code
https://claude.ai/code/session_01GCpfMCUMpco98QGbsuv2sr
Generated by Claude Code