-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Remove DefId
's Partial/Ord
impls
#122832
Remove DefId
's Partial/Ord
impls
#122832
Conversation
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Remove `DefId`'s `Partial/Ord` impls work towards rust-lang#90317 based on rust-lang#122824 and rust-lang#122820 r? `@michaelwoerister`
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (c92b8f5): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDBenchmarking 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 @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 671.97s -> 671.926s (-0.01%) |
Only rustdoc regressed |
@rust-lang/rustdoc how do I fix
|
In this case it means that your changes broke the search index generation apparently. Let me take a look at your code if I can see anything obvious. |
This PR looks great! Thanks, @oli-obk 🙂 @GuillaumeGomez, did you see anything that would explain the rustdoc test failure? |
… latter compares `DefId`s which we need to avoid
I worked around it, so there's no failure anymore in this PR. I'm coordinating with guillaume to fix it in a separate PR |
@bors r+ The rustdoc perf regressions are not ideal, but I don't think they should block merging. |
Oh I forgot to test, but they should be gone now, or at least smaller |
Fingers crossed 🙂 |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2781687): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 671.737s -> 668.256s (-0.52%) |
work towards #90317
based on #122824 and #122820
r? @michaelwoerister