rust/src/tools, branch stable

Do not attempt to compute size of a type with escaping lifetimes (#15434)

2025-09-11T11:51:59+00:00

A type with escaping bound vars cannot be wrapped in a dummy binder during size computation. Fixes rust-lang/rust-clippy#15429 changelog: [`zero_sized_hashmap_values`]: fix ICE in types with escaping lifetimes r? Jarcho ### Summary Notes - [Beta nomination](https://github.com/rust-lang/rust-clippy/pull/15434#issuecomment-3164866684) by [samueltardieu](https://github.com/samueltardieu) *Managed by `@rustbot`—see [help](https://forge.rust-lang.org/triagebot/note.html) for details*

Use aarch64-apple-darwin as the fallback doc source for `-apple-`

2025-08-21T15:46:29+00:00

We are moving away from `x86_64-apple-darwin`, so soon these docs won't be available. (cherry picked from commit 36a38206db1757dcf899644f758e6fc5a04141ad)

Revert #143031 and #140772 due to #144533

2025-08-15T15:17:03+00:00

Revert and due to the issue with host tools reported in . This reverts commits 508021aa4320f1feb4c7a783ee16c2feebc9249a and d577b39c5a39796e911f885c9a354074b52c25ab. The decision was made in . Tracking issue:

Auto merge of #144735 - weihanglo:update-cargo, r=weihanglo

2025-08-01T13:43:55+00:00

Update cargo 3 commits in a7fcef21feb4d835d1fee83b3f93b4aef86d5545..840b83a10fb0e039a83f4d70ad032892c287570a 2025-07-13 02:25:52 +0000 to 2025-07-30 13:59:19 +0000 - chore: fix some minor issues in comments (rust-lang/cargo#15787) - feat(schema): Expose `IndexPackage`, the description of a package within a Registry Index (rust-lang/cargo#15770) - chore: update toml/toml_edit to latest (rust-lang/cargo#15779) r? ghost

Rollup merge of #144751 - dalvescb:curtisd/aix_libextension, r=Noratrieb

2025-08-01T04:38:21+00:00

Add correct dynamic_lib_extension for aix AIX uses `.a` for static and shared libraries, this fixes a number of `run-make` tests on AIX

Rollup merge of #144691 - xizheyin:suggest-confuse, r=estebank

2025-08-01T04:38:20+00:00

Extend `is_case_difference` to handle digit-letter confusables This PR extends `is_case_difference` to handle digit-letter confusables Add support for detecting 0/O, 1/l, 5/S, 8/B, 9/g confusables in error suggestions. r? `@estebank`

add correct dynamic_lib_extension for aix

2025-07-31T19:49:23+00:00

Rollup merge of #144726 - jdonszelmann:move-attr-data-structures, r=lcnr

2025-07-31T15:19:40+00:00

merge rustc_attr_data_structures into rustc_hir this move was discussed on zulip: [#t-compiler > attribute parsing rework @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/attribute.20parsing.20rework/near/528530091) Many PRs in the attribute rework depend on this move.

Rollup merge of #144712 - nnethercote:dedup-num-types, r=fmease

2025-07-31T15:19:39+00:00

Deduplicate `IntTy`/`UintTy`/`FloatTy`. There are identical definitions in `rustc_type_ir` and `rustc_ast`. This commit removes them and places a single definition in `rustc_ast_ir`. This requires adding `rust_span` as a dependency of `rustc_ast_ir`, but means a bunch of silly conversion functions can be removed. r? `@fmease`

Rollup merge of #144688 - Stypox:better-enter-trace-span, r=RalfJung

2025-07-31T15:19:37+00:00

Uniform `enter_trace_span!` and add documentation 1. The latest changes to `enter_trace_span!` were ported from Miri (see https://github.com/rust-lang/miri/pull/4452#discussion_r2204958019), so now both the `rustc_const_eval` and the Miri macro accept the same syntax. Furthermore, the Miri macro was changed to just call rustc_const_eval`'s, to avoid duplication. 2. I made the `layout_of` (& friends) calls use that new syntax, e.g. `enter_trace_span!(layouting::layout_of, ...)` 3. I made sure the macro specifies all types/traits/macros it refers to using `$crate::`, so the macro works anywhere independently of which types/traits/macros are imported in the context it is used in. 4. I added documentation, examples and tips to the macro's doc. To make the rustdoc compile I had to add some hidden lines (`#`), but now it acts as a compilation test which will avoid reintroducing issue 3. in the future. I will also create a documentation file with everything one needs to know about tracing at a later point, but I figured adding some of that info directly on the tracing macro makes it more discoverable. 5. In `stack.rs` I made it so that the `"frame"` span has a field named "frame" (instead of "message") with the data about the frame. This field used to be called "message" (tracing's default) since it was previously formatted using `"{}", instance`, and now I replaced it with `frame = %instance`.