-
Notifications
You must be signed in to change notification settings - Fork 13k
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: Reduce clean::Type size #93963
Conversation
Some changes occurred in cc @camelid |
Let's check perf results: @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 39bfc5aa215b429e93a6427fe9181b405a984c4c with merge f411aa6adf39ffb096ce20832581c5b35b0da171... |
☀️ Try build successful - checks-actions |
Queued f411aa6adf39ffb096ce20832581c5b35b0da171 with parent c26fbf8, future comparison URL. |
Finished benchmarking commit (f411aa6adf39ffb096ce20832581c5b35b0da171): comparison url. Summary: This benchmark run did not return any relevant results. 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 |
Almost no changes on perf and small improvement on max rss. I'm a bit disappointed... :'( |
Even if there's not an immediate perf effect, getting rid of that field altogether is a good cleanup. |
39bfc5a
to
e4c4ffa
Compare
Updated! |
e4c4ffa
to
a2e35fa
Compare
@camelid I was able to do it by passing down the current (aka "real") |
This comment has been minimized.
This comment has been minimized.
a2e35fa
to
e38d16a
Compare
And of course I forgot to run |
☔ The latest upstream changes (presumably #96431) made this pull request unmergeable. Please resolve the merge conflicts. |
e38d16a
to
aab986b
Compare
Fixed merge conflict. |
☔ The latest upstream changes (presumably #96883) made this pull request unmergeable. Please resolve the merge conflicts. |
aab986b
to
2e1369c
Compare
Fixed the conflict. |
Sorry, I don't think I understand this code well enough to do a proper review. r? rust-lang/rustdoc |
This looks fine to me. It's moving a computation to happen earlier, so it stores a boolean instead of a DefId. GitHub Tip: This change isn't actually very big. Use /~https://github.com/rust-lang/rust/pull/93963/files?w=1 to ignore most of the indentation changes. @bors r+ |
📌 Commit 2e1369c has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (5f33adc): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
There is no need to keep the
DefId
around since it's allow used to compute if we should show a cast or not. As such, we can simply directly store the boolean.I think it's not what you had in mind @camelid but I guess it's still an improvement? 😉
It was discussed in #93941.
r? @camelid