I don’t think there’s an std-way of doing it, but the Rust ecosystem has this thing where people usually settle around one library. In this case, it is tokio. Afaik, most async stuff is done using tokio. What little async I’ve used, it’s been using tokio or some library like actix-web that uses tokio under the hood.
Also, side note, I never understood the idea of why golang is ugly. I think it’s fine, except for maybe the repeated if err != nil guards. Those are ugly. I wish it used additive types for error handling.
I don’t think there’s an
std-way of doing it, but the Rust ecosystem has this thing where people usually settle around one library. In this case, it istokio. Afaik, most async stuff is done usingtokio. What littleasyncI’ve used, it’s been usingtokioor some library likeactix-webthat usestokiounder the hood.Also, side note, I never understood the idea of why
golangis ugly. I think it’s fine, except for maybe the repeatedif err != nilguards. Those are ugly. I wish it used additive types for error handling.