Make some clean::Trait fields computation on demand#99598
Make some clean::Trait fields computation on demand#99598bors merged 1 commit intorust-lang:masterfrom
Conversation
|
Some changes occurred in src/librustdoc/clean/types.rs cc @camelid |
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
|
⌛ Trying commit edb9add with merge 9cf9c1165517fc1279f15f86fa4e2364e0e52e8a... |
|
☀️ Try build successful - checks-actions |
|
Queued 9cf9c1165517fc1279f15f86fa4e2364e0e52e8a with parent e7a9c11, future comparison URL. |
notriddle
left a comment
There was a problem hiding this comment.
r=me if it's not a perf regression
|
Finished benchmarking commit (9cf9c1165517fc1279f15f86fa4e2364e0e52e8a): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
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. @bors rollup=never Footnotes |
|
@bors r+ |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (ffa7733): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. 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 |
r? @notriddle