Conversation
|
r? @cjgillot (rust-highfive has picked a reviewer for you, use r? to override) |
|
@bors r+ rollup |
|
📌 Commit fb656b2856eeda61c3aa36fa6d2ac67ac03f2bee has been approved by |
|
@bors rollup=never -- with this many changes we could get weird perf effects, though hopefully not |
|
⌛ Testing commit fb656b2856eeda61c3aa36fa6d2ac67ac03f2bee with merge 24bbf29cb149e63a9a530d7e3e227235f64c87f8... |
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
Seems spurious... @bors retry |
|
☔ The latest upstream changes (presumably #89435) made this pull request unmergeable. Please resolve the merge conflicts. |
fb656b2 to
759eba0
Compare
|
@bors r=cjgillot |
|
📌 Commit 759eba0 has been approved by |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (b27661e): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
|
Seems like there is a small perf regression, no? |
|
Indeed, our heuristics did not deem this definite, but did consider it probable. We're working on those. Tagging as a regression. Likely to be painful to investigate, but we'll see. |
I'm currently working on allowing clippy to run on librustdoc after a discussion I had with @Mark-Simulacrum. So in the meantime, I fixed a few lints on the compiler crates.