-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
upgrade tokio to latest version(v0.3) #595
Conversation
fix executor other than tokio Co-authored-by: Héctor Ramón <hector0193@gmail.com>
Before merging, I think it may be better to wait a bit until most of the async ecosystem upgrades to the latest A bunch of examples are using |
Tested locally, and this works for the Game of Life and Solar System example programs. |
As I mentioned, We could use the compatibility layer, but it's probably better to wait for a bit. |
This feature allows users to rely on the `0.2` version of `tokio` while the async ecosystem upgrades to the latest version.
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 have introduced a new tokio_old
feature flag to allow users to enable the old tokio
and transition once the ecosystem is ready.
I think we can merge this. Let me know what you think!
I think we can merge it |
I have rolled back the latest changes to We should try to keep the repository decoupled from specific dev environments. For that purpose, you should change the |
It seems I forget checkout a new branch, sorry for the inconvenient |
No description provided.