Skip to content
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

Overview: document how Tokio fits in with the rest of the async ecosystem #80

Open
nrc opened this issue Oct 24, 2018 · 0 comments
Open

Comments

@nrc
Copy link

nrc commented Oct 24, 2018

Ideally this would be in the overview chapter, but it could fit in 'getting started' or as some kind of appendix.

I think it would be good to mention where Tokio sits in the wider context, in particular: the futures crate, the futures bits and pieces in libstd, async/await in the language, mio, and other related crates.

Not sure if this is related or a separate thing, but I think it would be good to clarify to what extent "io" in these docs means network io - can tokio be used for non-network io? How common is that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant