-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
use fold_list
in try_super_fold_with
for SubstsRef
#93643
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 711e736 with merge c892b04cd5f8abc1f132abbd4a14189de449a421... |
☀️ Try build successful - checks-actions |
Queued c892b04cd5f8abc1f132abbd4a14189de449a421 with parent 4e8fb74, future comparison URL. |
Finished benchmarking commit (c892b04cd5f8abc1f132abbd4a14189de449a421): comparison url. Summary: This benchmark run shows 55 relevant improvements 🎉 to instruction counts.
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 |
@michaelwoerister it probably makes sense to merge this PR by itself as without this change, #93505 is actually a regression in some cases and I don't want to hide that. Will look a bit more into #93505 separately |
📌 Commit 711e736 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (926e784): comparison url. Summary: This benchmark run shows 56 relevant improvements 🎉 to instruction counts.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
split out from #93505 as this by itself is responsible for most of the perf improvements there
r? @michaelwoerister