-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Assoc item cleanup Part 2 #90827
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
Assoc item cleanup Part 2 #90827
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit ba518ff with merge 717bcdb0d82f4a18a9cff553838f6c6c28599f5b... |
☀️ Try build successful - checks-actions |
Queued 717bcdb0d82f4a18a9cff553838f6c6c28599f5b with parent e4c23da, future comparison URL. |
Finished benchmarking commit (717bcdb0d82f4a18a9cff553838f6c6c28599f5b): comparison url. Summary: This change led to moderate relevant regressions 😿 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
Investigating locally, the change looks spurious. Looking at the history of these tests shows that a similar change happened when #89550 was merged and then later disappeared. |
Ok, let's go ahead. |
📌 Commit ba518ff has been approved by |
⌛ Testing commit ba518ff with merge 776c5d7b9ade1b3ddc57906ae020317db109e806... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (b053550): 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 |
AssocItem
fromRegionVariableOrigin::AutoRef
associated_item_def_ids
query instead of theassociated_items
query when possibleThe change to
ObligationCauseCode
from #90639 is omitted because it caused a perf regression.r? @cjgillot