-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Add an early-exit to QueryNormalizer::fold_ty
#68606
Conversation
This comment has been minimized.
This comment has been minimized.
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit 474d0e3 with merge 0c5d24e029a4ba74ad3647cefef127bf15ae6200... |
This comment has been minimized.
This comment has been minimized.
@bors rollup=never since this is a perf win, and we want to avoid masking regressions from other PRs in the rollup. |
Seems like we already did the perf testing @bors try- |
@bors r+ |
📌 Commit 474d0e3 has been approved by |
@bors p=1 |
☀️ Test successful - checks-azure |
Re-land "add IntoFuture trait and support for await" Testing the code from #65244 to see if the performance regressions are still there. #68606 and #68672 made perf optimizations that might interact with this change. If this lands, fixes #67982. cc @seanmonstar @jonas-schievink r? @cramertj
Pulled out from #68524, this results in a ~60-70% reduction in compile time for the await-call-tree benchmarks. This should unblock #67982 as well.
r? @Zoxc