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

Wrong assumption on chapter ordering #534

Open
ineol opened this issue Dec 26, 2020 · 1 comment
Open

Wrong assumption on chapter ordering #534

ineol opened this issue Dec 26, 2020 · 1 comment

Comments

@ineol
Copy link
Contributor

ineol commented Dec 26, 2020

The chapter about select assumes the Future trait has not yet been discussed, even though it is the chapter just after the Async in depth chapter:

This error isn't very clear and we haven't talked much about Future yet either. For now, think of Future as the trait that must be implemented by a value in order to call .await on it

@barafael
Copy link
Contributor

barafael commented Sep 1, 2022

Ironically, I was just about to report that the Async-in-depth chapter should come after the chapter on select, as select is a very practical and important concept. Perhaps the Async-in-depth chapter could be split into a part which discusses the future trait and then another part which really goes in depth. Then the order could be

  • Futures
  • Select
  • Async in depth

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

2 participants