Rollup of 7 pull requests - #162284
Open
JonathanBrouwer wants to merge 95 commits into
Open
Conversation
- Organize by "About" -> "Contributing" -> "Editing" -> "Maintaining" rather than mixing sections - Deduplicate a few lines into the guide itself - Recommend `mdbook serve` over `mdbook build` - Document `mdbook` layout and link to the upstream docs - Document sembr and that relative links must use `.md` extensions - Add a section on testing the tools in `ci/`
Fix some typos
Make README more complete and easier to follow
Dedup a bunch of information that's already on Forge
Rename LTA to CTA
This updates the rust-version file to da51146.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@da51146 Filtered ref: rust-lang/rustc-dev-guide@d9692a1 Upstream diff: rust-lang/rust@2c39ff4...da51146 This merge was created using https://github.com/rust-lang/josh-sync.
Rustc pull update
…l/mir-tyck Expand on MIR type checking.
ci: bump gha checkout action to latest
That is not all it does
fix "all x does is call ./x"
Installing cargo tools (`cargo install`) without locked dependencies exposes users to supply-chain attacks to all the dependencies of the tool (https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref/). Using `cargo install --locked` reduces this risk to a compromise of the tool itself, while using the locked and hashed version of the dependencies. I went through all `rg "cargo install"` hits in the repository and added `--locked` to all but explanatory examples (such as cargo's docs on `cargo install` itself). I validated that those tools publish functioning `Cargo.lock`s with https://gist.github.com/konstin/bcb1169c1c1120c259dca64e777a64d0.
- remove discouraging "pretty simple" in a complex chapter - mention that queries are demand-driven, not just memoized - emphasize that "query system" is a term of art (c.f. "Improper Nouns": https://siderea.dreamwidth.org/1773806.html)
touch-ups to "query system" chapter
…ocked Install cargo tools with locked dependencies
fix outdated docs about what RA config `x setup` generates
Add a central index of dev-guide reading club discussions
add some more compiler internals videos
…alle sanitizers: Implement support for the sanitize ignorelist The sanitize ignorelist gives central controls over which functions, files, etc. should be ignored and not sanitized. It is a common file format for clang and explained here: https://clang.llvm.org/docs/SanitizerSpecialCaseList.html. This change adds support for this list in Rust as well. r? @rcvalle
c-variadic: use `emit_ptr_va_arg` for `va_arg` on `sparc` I've built GCC for the target and validated pretty extensively that this works. Using our helper does generate worse code for `i64` unfortunately, I've reported that as llvm/llvm-project#214594. But, given that this is a tier-3 target etc. I don't think it makes sense to go out of our way to do better, we can just wait for LLVM to resolve that issue.
make -Ctarget-feature warnings more explicitly FCWs In rust-lang/compiler-team#994 we agreed that > We also change the warning emitted for unknown features in -Ctarget-feature to be explicitly a future-compat warning, and eventually we make unknown features in -Ctarget-feature a hard error. This PR implements that. I also created a new tracking issue specifically for this FCW as the old one has all sorts of discussion about us even figuring out the problem in the first place: rust-lang#162235.
…ray, r=mu001999 Generalize Decodable impl for arrays to all types This is almost the only impl that is not symetric with its Encodable counterpart. I tried to find out why in the history but it looks like this impl predates most of the generic symetric ones that are in this file, so it looks like it's not intentional. I bumped into this randomly by changing a Vec to an array in some Mir types. The error was pretty confusing and It took me a while to figure out so I think it's worth generalizing this for somebody else in the future, even though it's technically not necessary at the moment. ~~We piggyback off of `SmallVec` impl to avoid adding a `Default` bound or `MaybeUninit` unsafe dance. This moves the assert from the begining to the end of the loop.~~ We use `array::from_fn`
…ethercote
Update internal docs & tests to use `!` rather than `Infallible` in relation to `Try`
- Update docs, internal comments and tests to use `!` rather than `Infallible` in `Try` situations.
- Add a custom `enum Uninhabited {}` to specific clippy tests where unintentional future divergence in handling `!` vs other uninhabited types may be a possible concern
Refs:
- Never is ~~meow~~ now rust-lang#155499
- Try: rust-lang#84277 & rust-lang/goals#654
…r=fee1-dead Clean up the AST visitor The AST visitor is macro-heavy and complicated. This PR simplifies some aspects of it. Details in individual commits. r? @fee1-dead
rustc-dev-guide subtree update Subtree update of `rustc-dev-guide` to rust-lang/rustc-dev-guide@a6da162. Created using https://github.com/rust-lang/josh-sync. r? @ghost
rustbot
added
A-attributes
Member
Author
|
@bors r+ p=5 |
Contributor
rust-bors
Bot
added
S-waiting-on-bors
Contributor
rust-bors Bot
pushed a commit
that referenced
this pull request
Sep 4, 2026
…uwer Rollup of 7 pull requests Successful merges: - #157808 (sanitizers: Implement support for the sanitize ignorelist) - #160660 (c-variadic: use `emit_ptr_va_arg` for `va_arg` on `sparc`) - #162237 (make -Ctarget-feature warnings more explicitly FCWs) - #160111 (Generalize Decodable impl for arrays to all types) - #162174 (Update internal docs & tests to use `!` rather than `Infallible` in relation to `Try`) - #162226 (Clean up the AST visitor) - #162281 (rustc-dev-guide subtree update)
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
18 participants
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.
Successful merges:
emit_ptr_va_argforva_argonsparc#160660 (c-variadic: useemit_ptr_va_argforva_argonsparc)!rather thanInfalliblein relation toTry#162174 (Update internal docs & tests to use!rather thanInfalliblein relation toTry)r? @ghost
Create a similar rollup