Asynchronous Programming in Rust book
rust-lang.github.io
Asynchronous Programming in Rust book
1–10 of 46 posts
Re: Asynchronous Programming in Rust book
#2Sounds like an interesting book, the Rust Programming Language book was a great read (https://doc.rust-lang.org/stable/book/)
Re: Asynchronous Programming in Rust book
#3This book is largely a work in progress, still -- note all of the TODO's. Async-await designs have to stabilize before the rest is done.
Re: Asynchronous Programming in Rust book
#4Also known as: collaborative multitasking.
Re: Asynchronous Programming in Rust book
#5There isn't too much activity on this book [1] but I definitely think that more documentation about async programming in Rust is needed. Just recently I wanted to do something in async Rust and it's just such a PITA. I'm writing Rust since 3-4 years now and async throws me back to those first days where I didn't know how to cope with the error messages. Hopefully async/await syntax will improve this experience, but even then I think that documentation is needed. The futures crate is severely underdocumented. I'd love to have an example snippet next to each combinator etc.
Re: Asynchronous Programming in Rust book
#6Is it just me, or is the fact that the most important part:
https://rust-lang.github.io/async-book/getting_started/state...
Is missing, somewhat ironic?
Feels very much like the state of async matches the state of the guide. :P
What is the state of async? Is it close? Is it still changing with the futures 0.3-beta not finalized?
Are we six months away? A year?
Re: Asynchronous Programming in Rust book
#7Is it just me, or is the fact that the most important part: https://rust-lang.github.io/async-book/getting_started/state... Is missing, somewhat ironic? Feels very much like the state of async matches the state of the guide. :P What is the state of async? Is it close? Is it still changing with the futures 0.3-beta not finalized? Are we six months away? A year?
You can track the progress of the remaining issues here:
Re: Asynchronous Programming in Rust book
#8I think I'm correct in saying you don't need tokio for async but it seems all non-toy code uses it. Are there any alternatives to tokio out there for writing real async code or is the idea to build everything on it? As if it was std, but it's not... right?
Re: Asynchronous Programming in Rust book
#9Is it just me, or is the fact that the most important part: https://rust-lang.github.io/async-book/getting_started/state... Is missing, somewhat ironic? Feels very much like the state of async matches the state of the guide. :P What is the state of async? Is it close? Is it still changing with the futures 0.3-beta not finalized? Are we six months away? A year?
You can track the progress of the remaining issues here: https://areweasyncyet.rs/
I know, but I still struggle to get a handle on the state of it really.
What is going on with futures 0.3? Why is everyone still using 0.1?
How does that relate to these issues?
It superficially appears like the whole async story is still in a concept stage...
Re: Asynchronous Programming in Rust book
#10I think I'm correct in saying you don't need tokio for async but it seems all non-toy code uses it. Are there any alternatives to tokio out there for writing real async code or is the idea to build everything on it? As if it was std, but it's not... right?
If you need less abstractions over protocols, you might look into [mio](https://github.com/carllerche/mio).