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
Update tokio
to 1.0
#437
Comments
I'm happy to do it but let me take a look at the upstream dependencies. |
The main blocker seems to be actix-server which is still using mio 0.6. |
Just hit this as a problem when I updated Easily fixed locally by just not updating, but would be nice to be able to keep everything up to date. |
For that, you may have success with the compat layer for 2-3 migration. |
Would suggest remain on tokio 0.2 for the time being. There is no clear timeline for the blocking upstream deps that are still on tokio 0.2. |
Same with Compat only works the other way around, running 0.2 code on 0.3, but Actix itself uses 0.2 internally. |
There is no much actix-web can do when upstream deps are still stick with tokio 0.2. Adding the fact that tokio 0.3 is considered a beta for the upcoming tokio 1.0. There is really not much improvement for now from 0.2 and you would soon rush to tokio 1.0 again. For a project like actix-web it's not a good idea to rush for every new release unless there is a strong reason. If some of crate you use moves on early and push critical fixes exclusively for tokio 0.3. It's better to ask them the possibility of a backport for the time being. |
just a heads up... tokio 1.0 just came out today |
@robjtede @JohnTitor it would be helpful to have a final 0.11.0 version tagged which includes this tokio bump, as it would unblock dependencies updates in consumers. |
New version of tokio is released
tgbot vesrion of tokio is 0.2 Cargo.toml
Better upgrade, to avoid downloading two versions of tokio in projects
The text was updated successfully, but these errors were encountered: