4 ms·
If Rust does decide to continue with async, they should really look into investing in improved docs and education around it. When I was looking at it a few year
by daenz 4y ago
If Rust does decide to continue with async, they should really look into investing in improved docs and education around it. When I was looking at it a few years ago (maybe it has improved since then), I really did feel stupid for not getting the ideas/conventions/reasoning. If it was that off-putting to me, as someone with some experience, I can imagine it is very unapproachable to complete newcomers. It just felt like I was looking at something that shipped way too early.
- ollien 4y agoThe async chapter in Rust for Rustaceans was a great introduction. It leaves something to be desired because you walk away with it without knowing how to run any async code (it doesn't mention any runtimes, for instance), but it explains the concepts really well.
- Karrot_Kream 4y agoAsync is new enough that the function and trait docs are getting better all the time. There was a time it was really ugly to use async, and I still find it a bit crufty but it's a lot more approachable for someone new to Rust.
- zozbot234 4y agoIt's happening, see https://github.com/rust-lang/wg-async https://github.com/rust-lang/wg-async . Everyone is aware that current async support in Rust is very much at "MVP" status.