This adds a section that covers streams and tasks which are the final two topics needed to implement an echo server (which will be the section's closing example). These also represent two very important ideas that are needed for basically any Tokio project. Streams are a natural extension of Futures and Tasks make the Tokio's Futures different from most other languages (and more in the realm of Go or Erlang).
At first, I simply added a new section that contained content on Streams and Tasks but this felt disjointed. Instread this section breaks the previous "Futures" section up and moves the "Runtime" part into a new section with Tasks. Streams moves into the section Futures.
This adds a section that covers streams and tasks which are the final two topics needed to implement an echo server (which will be the section's closing example). These also represent two very important ideas that are needed for basically any Tokio project. Streams are a natural extension of Futures and Tasks make the Tokio's Futures different from most other languages (and more in the realm of Go or Erlang).
At first, I simply added a new section that contained content on Streams and Tasks but this felt disjointed. Instread this section breaks the previous "Futures" section up and moves the "Runtime" part into a new section with Tasks. Streams moves into the section Futures.