Merge train: #9736 + three commits missed by stale-head picks - #9737
Merged
Conversation
added 5 commits
September 4, 2026 17:03
The reordered initializer scan is a superset, not a replacement: a self-recursive arrow, a named function expression, and a binding whose initializer both creates a closure over it and is called immediately all passed before this change and must keep passing. Verified identical on both arms of the same-commit A/B.
This was referenced Sep 4, 2026
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
1 participant
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.
Merge train: #9736, plus three commits recovered from PRs I landed with a stale head.
The mistake this corrects
Merge trains cherry-pick from
refs/pull/<n>/headfetched at assembly time. If an author pushes reviewed follow-ups between the fetch and the train, the train lands the pre-review version. I caught that on #9697 (re-fetched, took the author's betteracross_mutform) and then failed to re-check before assembling trains 119 and 120.An audit of every PR landed today, by patch-id (
git cherry, which survives the SHA rewrite that rebase-merge performs — a SHA comparison reports every rebase-merged PR as unlanded and is useless here), found four gaps. Three are recovered below; the fourth was already fixed by #9736.gc/arena_right_size.rskept a rawthread_local!and the changelog mislabelled decimal bytes as MiB. That raw declaration was a newtls-budgetfailure onmain: the file count went from five to six. With this it is back to the five pre-existing ones (fs/deferred.rs,gc/census.rs,gc/idle_compact.rs,gc/idle_reclaim.rs,gc/oldgen_defrag.rs), which belong to other authors and are theirs to convert or justify.changelog.d/9704-fresh-instance-prototype-replacement.mdwas never onmain.changelog.d/9733-uncarried-shape-descriptors.md, same.test_gap_9718_initializer_self_binding.tspinning the self-recursive shapes the old scan ordering served, pushed after the train was assembled.#9732 was checked and is fine:
git cherryflagged both its commits, butgit diff origin/main <head> -- gc/trace.rsis empty, so the landed content matches the PR head. Patch-id noise from differing commit boundaries, not missing content.Validation
64/64 lint gates (re-run after the three recovered commits, not just before);
cargo test -p perry-runtime gc::green;check_thread_localsback to the five pre-existing files.