-
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
Re-land "add IntoFuture trait and support for await" #68811
Conversation
@bors try |
Awaiting bors try build completion |
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
☀️ Try build successful - checks-azure |
Queued 976ac3b with parent 8417d68, future comparison URL. |
In case you haven't already, please also ensure #67757 doesn't get reintroduced. Thanks. |
@Arnavion Thanks for pointing to that, I'd indeed forgotten about the type length limit problem. I'm not quite sure what to do about it. We discussed this during the original PR (around here) and thought we had a fix for it in #65743, but that seems to have only been a partial fix. cc @eddyb The perf run seems to be done; results are not great for async benchmarks, but not a total disaster either. (This is far better than the original regression which led us to revert the change.) While it might be possible to land the change with this regression, I'd prefer to dig into it some more first. So, in summary, I think we need a fix to #67757, and to dig into the remaining performance regression. If anyone wants to take on either of these (or both), please feel free! |
@@ -521,7 +521,7 @@ impl<'hir> LoweringContext<'_, 'hir> { | |||
|
|||
/// Desugar `<expr>.await` into: | |||
/// ```rust | |||
/// match <expr> { | |||
/// match ::std::future::IntoFuture::into_future(<expr>) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think #69218 should help improve performance here - this PR appears to introduce many additional predicates during typeck, which end up getting stalled for several |
Triaged |
@tmandry any updates? |
Closing this due to inactivity |
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