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
refactor(runtime): hide internals from public-facing API, export tokio #1332
refactor(runtime): hide internals from public-facing API, export tokio #1332
Conversation
1c7e0ac
to
910806d
Compare
Cool! If the user wants a different version of tokio, cargo should use the one they specify in their Cargo.toml, right (as long as it's not a major version change, but that isn't planned for tokio)? |
Yes, the min version remains what we have in our Cargo.toml (1.22), and creating or bumping the lock file will choose the latest compatible one. |
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.
Looking good. It would w great to run a cargo check
on all our examples in case we missed anything with the review.
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.
We can merge if the dependencies improvement is not possible 😄
Description of change
finally a well isolated PR...
How has this been tested? (if applicable)