-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustdoc: Cleanup clean::Impl
and other parts of clean
#90675
Conversation
It can be computed on-demand in `Item::span()`.
This change has two advantages: 1. It makes the possible states clearer, and it makes it impossible to construct invalid states, such as a blanket impl that is also an auto trait impl. 2. It shrinks the size of `Impl` a bit, since now there is only one field, rather than two.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 7c7bf45 with merge f6043fd4839769bd32477215f74a9315cbbb8e74... |
☀️ Try build successful - checks-actions |
Queued f6043fd4839769bd32477215f74a9315cbbb8e74 with parent fecfc0e, future comparison URL. |
Finished benchmarking commit (f6043fd4839769bd32477215f74a9315cbbb8e74): comparison url. Summary: This change led to small relevant improvements 🎉 in compiler performance.
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 led to changes in compiler perf. @bors rollup=never |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you remove the Clean impls that was used? That seems like a lot of churn for not a ton of benefit ... the rest of the commits are great though :)
Overall, the reasons are as follows:
I also have specific reasons for each removed impl (except for the unused
|
r=me with #90675 (comment) done :) @bors rollup=never |
The `ImplKind` methods can just be used directly instead.
Done! @bors r=jyn514 rollup=never [you can never say rollup=never too many times ;)] |
📌 Commit b5817fa has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (3e3890c): comparison url. Summary: This change led to moderate relevant improvements 🎉 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
This PR cleans up and reduces the size of
clean::Impl
, makes some other small performance improvements, and removes some Clean impls that are either unnecessary or potentially confusing.r? @jyn514