Skip to content

Rollup of 22 pull requests - #160517

Merged
rust-bors[bot] merged 165 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-u5PpQgB
Aug 5, 2026
Merged

Rollup of 22 pull requests#160517
rust-bors[bot] merged 165 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-u5PpQgB

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Contributor

Successful merges:

Failed merges:

r? @ghost

Create a similar rollup

ChayimFriedman2 and others added 30 commits May 6, 2026 23:50
But only if the source is code passed to the macro, not code inside the macro.
With `#[allow(rust_analyzer::inactive_code)]`.
See added comment for rationale. Also note that `rand` has defaulted to
LE for many years, apparently without any objections.
Currently JsonLinesParser::from_line is called for both stdout and
stderr, so trait implementers cannot distinguish stdout and stderr.

Define a separate JsonLinesParser::from_stderr_line to make the
stdout/stderr distinction explicit, and update use sites. This is not
a behaviour change.

AI disclosure: Partially written by Codex and GPT-5.5.
…lens

fix: Respect `references.exclude[Tests/Imports]` in references lens
feat: Support inactive-code diagnostic in macros
When encountering a for loop that requires a mutable iterator item, we previously suggested changing the method on the iterated expression, but ignored bindings. We now go to the binding's definition and suggest changing the method there too.

```
error[E0594]: cannot assign to `v.v`, which is behind a `&` reference
  --> $DIR/suggest-mut-method-for-loop-hashmap.rs:31:9
   |
LL |     for (_k, v) in x {
   |                    - this iterator yields `&` references
...
LL |         v.v += 1;
   |         ^^^^^^^^ `v` is a `&` reference, so it cannot be written to
   |
help: use mutable method
   |
LL |     let mut x = map.iter_mut();
   |                         ++++
```
Previously we read both stdout and stderr in the discover
protocol. Depending on the tool generating rust-project JSON, this
meant that a single stderr log message could break discovery.

Instead, only look for JSON from the discover command's stdout, and
forward stderr to the rust-analyzer logs.

Update both the implementation and the discover protocol docs to
reflect this behaviour.

AI disclosure: Code partly written by GPT-5.5.
fix: Discover protocol should only parse stdout
fix: resolve path on all namespace on resolve_path
I noticed a few "its" versus "it's" grammatical issues, so I've done a
pass at fixing obvious grammar issues.

AI disclosure: I fixed the first few manually, then asked GPT-5.5 to
look for additional cases and kept all the obviously reasonable fixes.
Signed-off-by: Amirhossein Akhlaghpour <m9.akhlaghpoor@gmail.com>
…4-unicode-progress-report

fix: make analysis-stats progress bar Unicode-safe
…_a_discriminant_type_larger_than_typeck_s

fix: don't pick a discriminant type larger than typeck's
@JonathanBrouwer

Copy link
Copy Markdown
Contributor Author

@bors p=10
Scheduling

@rust-bors

rust-bors Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: 298475b (298475b611506c375c002324ae925ee9a47bf9af)
Base parent: 1ed2df6 (1ed2df61a19042f231709eb05d032ae9e2cb2084)

@samueltardieu

Copy link
Copy Markdown
Member

@JonathanBrouwer If this goes first, this will conflict with the clippy subtree update which will need to be made again from scratch because of a conflict in src/tools/clippy/tests/ui/suspicious_arithmetic_impl.rs.

@rust-bors

This comment has been minimized.

@rust-bors rust-bors Bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Aug 5, 2026
@rust-bors

rust-bors Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 25m 19s
Pushing 7218ebe to main...

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor
What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 1ed2df6 (parent) -> 7218ebe (this PR)

Test differences

Show 952 test diffs

Stage 0

  • core::builder::cli_paths::tests::x_test_rustdoc_skip_rustdoc: [missing] -> pass (J2)
  • core::builder::cli_paths::tests::x_test_src_tools_miri_and_cargo_miri: [missing] -> pass (J2)
  • core::builder::tests::test_intersection: pass -> [missing] (J2)
  • cli::progress_report::tests::shorter_unicode_message_clears_overlap: [missing] -> pass (J3)
  • expr_store::scope::tests::pattern_type_expr_scope: [missing] -> pass (J3)
  • handlers::inline_macro::tests::inline_macro_in_included_file: [missing] -> pass (J3)
  • handlers::mismatched_arg_count::tests::arg_count_multi_arg_closure: [missing] -> pass (J3)
  • handlers::type_mismatch::tests::type_mismatch_collision_in_generic: [missing] -> pass (J3)
  • handlers::type_mismatch::tests::type_mismatch_no_collision_unchanged: [missing] -> pass (J3)
  • handlers::unlinked_file::tests::unlinked_file_with_reserved_keyword_abstract: [missing] -> pass (J3)
  • handlers::unlinked_file::tests::unlinked_file_with_strict_keyword_move: [missing] -> pass (J3)
  • handlers::unlinked_file::tests::unlinked_invalid_symbol_in_module_name: [missing] -> pass (J3)
  • syntax_editor::tests::test_more_times_insert_node_to_same_node: [missing] -> pass (J3)
  • syntax_editor::tests::test_more_times_replace_node_to_same_token: [missing] -> pass (J3)
  • syntax_highlighting::tests::mod_and_macro_name_conflict: [missing] -> pass (J3)
  • syntax_highlighting::tests::private_multi_namespace: [missing] -> pass (J3)
  • syntax_highlighting::tests::test_raw_string_format_specifiers: [missing] -> pass (J3)
  • tests::regression::braced_const_path: [missing] -> pass (J3)
  • tests::regression::regression_22799: [missing] -> pass (J3)
  • tests::runner::ok::closure_postfix_range_method_call: [missing] -> pass (J3)
  • tests::traits::recursive_auto_trait: [missing] -> pass (J3)

Stage 1

  • [ui (polonius)] tests/ui/coherence/cross-crate-specialization-check.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/higher-ranked/hrtb-projection-closure-62201.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/impl-trait/malformed-tait-impl-with-const-param.rs#incr: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/impl-trait/malformed-tait-impl-with-const-param.rs#normal: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/issues/issue-38412.rs: pass -> [missing] (J0)
  • [ui (polonius)] tests/ui/issues/issue-38875/issue-38875.rs: pass -> [missing] (J0)
  • [ui (polonius)] tests/ui/issues/issue-41652/issue-41652.rs: pass -> [missing] (J0)
  • [ui (polonius)] tests/ui/issues/issue-50264-inner-deref-trait/result-as_deref.rs: pass -> [missing] (J0)
  • [ui (polonius)] tests/ui/issues/issue-50865-private-impl-trait/main.rs: pass -> [missing] (J0)
  • [ui (polonius)] tests/ui/issues/issue-52140/main.rs: pass -> [missing] (J0)
  • [ui (polonius)] tests/ui/issues/issue-52705/main.rs: pass -> [missing] (J0)
  • [ui (polonius)] tests/ui/issues/issue-74236/main.rs: pass -> [missing] (J0)
  • [ui (polonius)] tests/ui/privacy/destructure-box-private-fields.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/rust-2018/uniform-paths/reexport-builtin-attr.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/target-feature/llvm-target-feature.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/traits/next-solver/borrowck-normalization.rs: [missing] -> pass (J0)
  • annotations::tests::refs_exclude_tests: [missing] -> pass (J4)
  • cli::progress_report::tests::shorter_unicode_message_clears_overlap: [missing] -> pass (J4)
  • config::tests::postfix_snippet_item_scope_is_invalid: [missing] -> pass (J4)
  • expr_store::scope::tests::inline_const_expr_scope: [missing] -> pass (J4)
  • handlers::inactive_code::tests::cfg_in_macro_does_not_diagnose_the_whole_call: [missing] -> pass (J4)
  • handlers::mismatched_arg_count::tests::arg_count_multi_arg_closure: [missing] -> pass (J4)
  • handlers::unlinked_file::tests::unlinked_file_with_reserved_keyword_abstract: [missing] -> pass (J4)
  • handlers::unlinked_file::tests::unlinked_file_with_strict_keyword_move: [missing] -> pass (J4)
  • handlers::unlinked_file::tests::unlinked_file_with_weak_keyword_safe: [missing] -> pass (J4)
  • handlers::unlinked_file::tests::unlinked_invalid_symbol_in_module_name: [missing] -> pass (J4)
  • handlers::unlinked_file::tests::unlinked_numeric_module_name: [missing] -> pass (J4)
  • mir::eval::tests::slice_get_unchecked_const_slice: [missing] -> pass (J4)
  • mir::eval::tests::slice_get_unchecked_out_of_bounds: [missing] -> pass (J4)
  • syntax_editor::tests::test_more_times_replace_node_to_mutable_token: pass -> [missing] (J4)
  • syntax_editor::tests::test_more_times_replace_node_to_same_token: [missing] -> pass (J4)
  • syntax_highlighting::tests::mod_and_macro_name_conflict: [missing] -> pass (J4)
  • syntax_highlighting::tests::test_raw_string_format_specifiers: [missing] -> pass (J4)
  • tests::regression::braced_const_path: [missing] -> pass (J4)
  • tests::regression::regression_22799: [missing] -> pass (J4)
  • tests::regression::regression_22820: [missing] -> pass (J4)
  • tests::regression::rpit_function_with_non_trivial_anon_const: [missing] -> pass (J4)
  • tests::traits::recursive_auto_trait: [missing] -> pass (J4)
  • vfs_path::tests::virtual_path_starts_with_is_component_based: [missing] -> pass (J4)
  • [ui] tests/ui/coherence/cross-crate-specialization-check.rs: [missing] -> pass (J5)
  • [ui] tests/ui/cross-crate/cross-crate-array-len.rs: [missing] -> pass (J5)
  • [ui] tests/ui/deref/option-result-as_deref.rs: [missing] -> pass (J5)
  • [ui] tests/ui/error-emitter/no-method-empty-span.rs: [missing] -> pass (J5)
  • [ui] tests/ui/higher-ranked/hrtb-projection-closure-62201.rs: [missing] -> pass (J5)
  • [ui] tests/ui/impl-trait/malformed-tait-impl-with-const-param.rs#incr: [missing] -> pass (J5)
  • [ui] tests/ui/impl-trait/malformed-tait-impl-with-const-param.rs#normal: [missing] -> pass (J5)
  • [ui] tests/ui/issues/issue-37725.rs: pass -> [missing] (J5)
  • [ui] tests/ui/issues/issue-41652/issue-41652.rs: pass -> [missing] (J5)
  • [ui] tests/ui/issues/issue-50264-inner-deref-trait/option-as_deref.rs: pass -> [missing] (J5)
  • [ui] tests/ui/issues/issue-50264-inner-deref-trait/result-as_deref.rs: pass -> [missing] (J5)
  • [ui] tests/ui/issues/issue-52705/main.rs: pass -> [missing] (J5)
  • [ui] tests/ui/issues/issue-74236/main.rs: pass -> [missing] (J5)
  • [ui] tests/ui/macros/macro-attr-feature-gate-cross-crate.rs: [missing] -> pass (J5)
  • [ui] tests/ui/privacy/destructure-box-private-fields.rs: [missing] -> pass (J5)
  • [ui] tests/ui/recursion/infinite-instantiation-via-size-increasing-tuple.rs: [missing] -> pass (J5)
  • [ui] tests/ui/rust-2018/uniform-paths/reexport-builtin-attr.rs: [missing] -> pass (J5)
  • [ui] tests/ui/rust-2018/uniform-paths/reexport-crate.rs: [missing] -> pass (J5)
  • [ui] tests/ui/traits/next-solver/borrowck-normalization.rs: [missing] -> pass (J5)
  • [ui] tests/ui/type-alias-impl-trait/nested-tait-inline-mir-validation.rs: [missing] -> pass (J5)
  • [ui] tests/ui/typeck/self-param-in-fn-item-cast-to-fn-trait.rs: [missing] -> pass (J5)
  • [ui] tests/ui/unboxed-closures/transmute-usize-to-rust-call-fn-ptr.rs: [missing] -> pass (J5)

Stage 2

  • [ui] tests/ui/coherence/cross-crate-specialization-check.rs: [missing] -> pass (J1)
  • [ui] tests/ui/higher-ranked/hrtb-projection-closure-62201.rs: [missing] -> pass (J1)
  • [ui] tests/ui/impl-trait/method/resume-without-personality-issue-159980.rs: [missing] -> pass (J1)
  • [ui] tests/ui/issues/issue-37291/main.rs: pass -> [missing] (J1)
  • [ui] tests/ui/issues/issue-41652/issue-41652.rs: pass -> [missing] (J1)
  • [ui] tests/ui/issues/issue-50264-inner-deref-trait/option-as_deref_mut.rs: pass -> [missing] (J1)
  • [ui] tests/ui/issues/issue-50264-inner-deref-trait/result-as_deref.rs: pass -> [missing] (J1)
  • [ui] tests/ui/issues/issue-50264-inner-deref-trait/result-as_deref_mut.rs: pass -> [missing] (J1)
  • [ui] tests/ui/issues/issue-52141/main.rs: pass -> [missing] (J1)
  • [ui] tests/ui/issues/issue-74236/main.rs: pass -> [missing] (J1)
  • [ui] tests/ui/recursion/infinite-instantiation-via-size-increasing-tuple.rs: [missing] -> pass (J1)
  • [ui] tests/ui/rust-2018/uniform-paths/reexport-crate.rs: [missing] -> pass (J1)
  • [ui] tests/ui/transmutability/unsafe-binder-opaque-type-layout.rs: [missing] -> pass (J1)
  • [ui] tests/ui/type-alias-impl-trait/nested-tait-inline-mir-validation.rs: [missing] -> pass (J1)
  • [ui] tests/ui/typeck/self-param-in-fn-item-cast-to-fn-trait.rs: [missing] -> pass (J1)
  • [ui] tests/ui/unboxed-closures/transmute-usize-to-rust-call-fn-ptr.rs: [missing] -> pass (J1)
  • [ui] tests/ui/target-feature/llvm-target-feature.rs: [missing] -> pass (J6)
  • [ui] tests/ui/issues/issue-49851/compiler-builtins-error.rs: ignore (gcc backend is marked as ignore) -> [missing] (J7)

(and 128 additional test diffs)

Additionally, 724 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 7218ebe93668f51a94a572b690c433dfdbdc2c3d --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. dist-armv7-linux: 1h 3m -> 1h 34m (+50.2%)
  2. x86_64-gnu-aux: 1h 51m -> 2h 45m (+48.5%)
  3. x86_64-msvc-ext2: 1h 13m -> 1h 46m (+46.4%)
  4. x86_64-gnu-stable: 1h 56m -> 2h 39m (+37.2%)
  5. i686-msvc-2: 1h 57m -> 1h 17m (-34.0%)
  6. x86_64-gnu-llvm-22-1: 59m 39s -> 1h 19m (+32.4%)
  7. dist-aarch64-apple: 2h 27m -> 1h 41m (-31.0%)
  8. i686-msvc-1: 2h 53m -> 1h 59m (-30.8%)
  9. x86_64-rust-for-linux: 50m 20s -> 36m 19s (-27.9%)
  10. dist-x86_64-mingw: 2h 7m -> 2h 40m (+26.2%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer

Copy link
Copy Markdown
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#160426 rust-analyzer subtree update 3595701221e66356d7d2a57df2e8fad03bf2a0ff (link)
#160372 Derive the allocator used by tools from rustc's allocator 82d6fff3c08c9402aaaa06354466c5b714163d83 (link)
#146882 fully deprecate the legacy integral modules 6fe81eef34dc7aac9a0b6fa4d5f18c8bebdee2e1 (link)
#158727 std: use readdir on nearly all UNIX platforms 80c2b50eb816f067200e5713ff55814ebce803e4 (link)
#159727 Various steps in moving away from the big reflection enum t… 114cbc07c0ce66bcef533c09dc2cf7ba53141f09 (link)
#160443 normalize in relations, not generalize, when relating infer… ba12bfb71804be59d5f5a88cbef74293ca88005c (link)
#160457 implement -Zllvm-target-feature bf72936c17990296889da995c31ff3f504385131 (link)
#160480 Single-pass ASCII lower/upper case conversion 4c170e142b071bc9726bffb23277308b21b17370 (link)
#160502 Reduce number of miri tests executed on PR CI f3f577cca059347429ddb616f789044b1b76841f (link)
#157430 std::random: use little-endian for reproducibility 8b5739df55adc6cc706dad99d3980234d3a98fa3 (link)
#158110 fix macro attribute feature-gate span 84474c37ddfbf535477c5c7f7dd92b71f1d571b7 (link)
#159975 Use real ThinVec in StmtDebugInfos 5c43d9040e85238255a630c8ed1699865db884d5 (link)
#160001 Suggest mutable method when iterating over binding fb0023df964c98a9fe0029ec9d4089a2aa3d1185 (link)
#160024 Fix mono reachability with no-op landing pads a3989e171e005d3a79329ab59a25054a7a0d1049 (link)
#160154 Add regression test for HRTB associated type projection clo… aca83309c2681773a1609a66e32e85205ca45c03 (link)
#160176 No more tests/ui/issues! 532f3964ea3841ca242daf9fd2317933ce4b9696 (link)
#160326 Remove hidden_glob_reexports 45d8f69f5661378bc68970bf1f675afabc197d1f (link)
#160407 Add regression tests for a number of ICEs and diagnostics i… f7d0d16f6f5f3b63e058ae3726adc48623357690 (link)
#160430 bootstrap: Don't produce mutated/filtered PathSets during c… 814f4abcb86947a4661d7670873fbb4d5540a2ed (link)
#160472 Minor fixes to core::io & alloc::io Documentation 2853a7cfade2b471b73a7c8d0583b546801fb397 (link)
#160486 Remove unused FreeRegionsVisitor b1042cf474fbdb6bb4942529b34498df4a606ffd (link)
#160496 clarify non-determinism docs for algebraic operations 8ecc3b7db5b340cbc799892b4a8c27191385ff4b (link)

previous master: 1ed2df61a1

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@JonathanBrouwer

JonathanBrouwer commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

@JonathanBrouwer If this goes first, this will conflict with the clippy subtree update which will need to be made again from scratch because of a conflict in src/tools/clippy/tests/ui/suspicious_arithmetic_impl.rs.

@samueltardieu Oops, I literally only just woke up so I didn't get the chance to let you go first, sorry.
In the future, feel free to reschedule PRs yourself <3
Let me know if there's anything I can do to help resolve this situation now that it happened

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (7218ebe): comparison URL.

Overall result: ❌ regressions - please read:

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

  • If the regression was expected or you think it can be justified,
    please write a comment with sufficient written justification, and add
    @rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
  • If you think that you know of a way to resolve the regression, try to create
    a new PR with a fix for the regression.
  • If you do not understand the regression or you think that it is just noise,
    you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
    were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
0.6% [0.2%, 1.9%] 11
Regressions ❌
(secondary)
0.5% [0.2%, 1.8%] 13
Improvements ✅
(primary)
-0.8% [-0.8%, -0.8%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.5% [-0.8%, 1.9%] 12

Max RSS (memory usage)

Results (primary -0.5%, secondary 1.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
2.1% [0.8%, 3.3%] 3
Regressions ❌
(secondary)
2.5% [0.4%, 6.2%] 6
Improvements ✅
(primary)
-2.5% [-4.2%, -0.5%] 4
Improvements ✅
(secondary)
-3.3% [-4.0%, -2.7%] 2
All ❌✅ (primary) -0.5% [-4.2%, 3.3%] 7

Cycles

Results (primary 1.0%, secondary 0.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
1.6% [0.4%, 3.1%] 5
Regressions ❌
(secondary)
4.7% [0.6%, 10.2%] 8
Improvements ✅
(primary)
-0.7% [-0.8%, -0.6%] 2
Improvements ✅
(secondary)
-2.7% [-15.2%, -0.4%] 11
All ❌✅ (primary) 1.0% [-0.8%, 3.1%] 7

Binary size

Results (primary 0.6%, secondary 1.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
0.7% [0.1%, 2.6%] 19
Regressions ❌
(secondary)
1.0% [0.1%, 2.0%] 2
Improvements ✅
(primary)
-0.3% [-0.6%, -0.1%] 3
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.6% [-0.6%, 2.6%] 22

Bootstrap: 489.825s -> 496.187s (1.30%)
Artifact size: 391.14 MiB -> 391.37 MiB (0.06%)

@rustbot rustbot added the perf-regression Performance regression. label Aug 5, 2026
WorldSEnder added a commit to WorldSEnder/wasm-tools that referenced this pull request Aug 6, 2026
`u32::max_value()` got deprecated last week as part of
rust-lang/rust#160517 in 0115f0ea2097fe72bc2b66c575ee98af5efb2d84
@JonathanBrouwer

This comment was marked as outdated.

@JonathanBrouwer

This comment was marked as outdated.

@JonathanBrouwer

JonathanBrouwer commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

All perf runs from this PR are getting similar perf regressions, this is likely some change to the benchmark server causing this, rather than a PR in this rollup @Kobzol
@rustbot label: +perf-regression-triaged

@rustbot rustbot added the perf-regression-triaged The performance regression has been triaged. label Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-CI Area: Our Github Actions CI A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. perf-regression Performance regression. perf-regression-triaged The performance regression has been triaged. rollup A PR which is a rollup T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rust-analyzer Relevant to the rust-analyzer team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.