Some changes occurred in src/tools/clippy

cc @rust-lang/clippy

Some changes occurred in need_type_info.rs

cc @lcnr

@bors try rust-timer queue

@bors try @rust-timer queue

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

⌛ Trying commit 6537d39 with merge f5b5768a77119ca3933b67223782ef7a3b238bb1...

☀️ Try build successful - checks-actions
Build commit: f5b5768a77119ca3933b67223782ef7a3b238bb1 (f5b5768a77119ca3933b67223782ef7a3b238bb1)

Queued f5b5768a77119ca3933b67223782ef7a3b238bb1 with parent 1cd72b7, future comparison URL.

Finished benchmarking commit (f5b5768a77119ca3933b67223782ef7a3b238bb1): comparison url.

Instruction count

• Primary benchmarks: no relevant changes found
• Secondary benchmarks: 😿 relevant regressions found

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf +perf-regression