-
Notifications
You must be signed in to change notification settings - Fork 145
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 to futures-0.2 and tokio instead of tokio-core #462
Comments
gluon 0.8 is using tokio instead of tokio_core |
Marwes
added a commit
to Marwes/gluon
that referenced
this issue
Jul 14, 2018
Closes gluon-lang#462 BREAKING CHANGE Upgrade to tokio
Marwes
added a commit
to Marwes/gluon
that referenced
this issue
Jul 17, 2018
Closes gluon-lang#462 BREAKING CHANGE Upgrade to tokio
Marwes
added a commit
to Marwes/gluon
that referenced
this issue
Jul 21, 2018
Closes gluon-lang#462 BREAKING CHANGE Upgrade to tokio
Marwes
added a commit
to Marwes/gluon
that referenced
this issue
Jul 24, 2018
Closes gluon-lang#462 BREAKING CHANGE Upgrade to tokio
Marwes
added a commit
to Marwes/gluon
that referenced
this issue
Jul 24, 2018
Closes gluon-lang#462 BREAKING CHANGE Upgrade to tokio
Marwes
added a commit
to Marwes/gluon
that referenced
this issue
Jul 26, 2018
Closes gluon-lang#462 BREAKING CHANGE Upgrade to tokio
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
gluon_vm
is the main user of futures which is where the bulk of the work needs to be done. Should be fairly straightforward to update since it doesn't do anything particularily crazy with async stuff.The text was updated successfully, but these errors were encountered: