I finished the 4th and final part to my "how I understood async/await in Rust" series of blog posts: https://hegdenu.net/posts/understanding-async-await-4/
In this one we look at doing something that can't be done without writing a "manual" future implementation. Namely writing an async channel.
Yesterday I published part 3 of my series on "how I finally understood async/await in #Rust".
The topic is "why shouldn’t I hold a mutex guard across an await point?".
There is another great post related to understanding async/await in #rust in @thisweekinrust 503.
How to think about `async`/`await` in Rust by @cliffle:
https://cliffle.com/blog/async-inversion/
I understand that it's not new so much as newly extraced from existing documentation. In any event, it's a great read if you're trying to wrap your head around async/await.
This post on Pin in #async #rust is fantastic!
https://ohadravid.github.io/posts/2023-07-put-a-pin-on-that/ by Ohad Ravid (@ohadrv on the bird site, doesn’t appear to be on mastodon)
If you’ve ever struggled to understand what Pin is trying to do and how it relates to all that Unpin and !Unpin stuff, have a read!
Found via @thisweekinrust 503.
#async #rust #rustlang #asyncrust
I recently heard about someone using #tokioConsole from a “custom runtime” (not using the `tokio_unstable` flag). I’m not sure if they meant custom #tokio or a non-tokio custom runtime.
Honestly, either of those happening is pretty cool. I’d love to hear from anyone else doing anything similar too!
#tokioconsole #tokio #rust #rustlang #asyncrust
I've finished part 2 of my series on "how I finally understood async/await in #Rust".
The topic is "how does a pending future get woken?".
@KevinWho @soulsource The Rust Foundation does maintain a library with the ability to execute asynchronous functions (https://crates.io/crates/futures), but they made the intentional decision to not include it in the standard library.
(I'd still recommend #tokio (https://crates.io/crates/tokio) as the go-to #AsyncRust runtime, though!)