-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[WIP] Refactor to use new futures api #2612
Conversation
f0e3f4e
to
9286854
Compare
9286854
to
3aab4b1
Compare
3aab4b1
to
f980a97
Compare
Can we temporarily switch to nightly for some time and move the code to async await? cc @ry |
You can do that in a branch :) Not in master. I don't want to open that can of worms. |
In that case, given the scale of refactoring we're doing at the moment, I think it is not worth it to maintain another branch. We'll do it when async-await is in stable |
Here is a list of dependencies, and their respective statuses.
Dependent on tokio:
I think that is everything let me know if there is something I missed. Also thoughts on runtime? |
I manged to get This branch:
Master:
Within margin of error, but still about ~2-3% in favor of this branch. |
@afinch7 That's good to hear! |
40323e0
to
80f5c39
Compare
Think most of the stuff can be checked except hyper-rustls (Perhaps use hyper-tls)? |
Yes I think most of the dependencies are ready, but async/await has been delayed to 1.39.0 that's really the only thing I'm still waiting on here. |
Old PR, closing. We will move to the new futures API, but ideally there would be a stable release of Tokio using this new future API first. We need Tokio to make a stable release using the new Futures API first. |
Currently depends on a alpha version of
futures-preview
, but withstd::future
now on stable we should get a stable release of futures 0.3 soon. Normally I would say wait on something like this, but #2385 is going to need this change to properly support async ops.