is a bit like and libev before that. It’s a lightweight IO library over the OS abstractions. Mio libuv are basically the same as promises. Java and C# also call them Futures. The futures library also provides , which are similar to Node streams but more strongly typed. Streams are to futures as arrays are to values. Streams can even be viewed as a using , where the resolved value is the next item in the stream along with the rest of the stream. This seems like a really neat feature. Futures streams Future into_future depends on / is built on top of Futures and Mio. This library provides the I/O primitives and event loop for async I/O in Rust. It’s the connection between futures and mio. For example, connecting a TCP stream returns a resolving to a TCP stream, and a TCP listener implements a stream of TCP streams (accepted connections). Tokio-core Future ::Core is an instance of an event loop (like that of which you get implicitly in JavaScript). Reactor seems to be a commonly used name for an event loop type object. Reactor is like setTimeout and is like setInterval. Timeout interval Those are the basics, so the should be fairly self-explanatory. is another good read on . examples Here Tokio a . fast base64 encoder and decoder is how hackers start their afternoons. We’re a part of the family. We are now and happy to opportunities. Hacker Noon @AMI accepting submissions discuss advertising &sponsorship To learn more, , , or simply, read our about page like/message us on Facebook tweet/DM @HackerNoon. If you enjoyed this story, we recommend reading our and . Until next time, don’t take the realities of the world for granted! latest tech stories trending tech stories

Facebook

Too Long; Didn't Read

Let Your Engineers & PMs focus on Product. Apply for $50K Credits!

Rust Async Libraries Cheat Sheet for Node.js Developers

Too Long; Didn't Read

Company Mentioned

@grantminer

RELATED STORIES