Eric Holk

I'm feeling pretty vindicated on behalf of my fourteen-year-old self.

I often find myself writing a function that internally defines a struct just so I can implement a trait on it and return that type as an impl Trait.

Lately I've been talking to a few people about whether it might be possible to replace the Pin wrapper in Rust with a new Move trait.

One of the big priorities for the Rust Leadership Council has been to determine the "shape of Rust."

There are currently two competing designs for async iteration traits for Rust.

When I last wrote about async cancellation in Rust, I touched briefly on the question of how cancellation interacts with panic.

While doing some housekeeping on my blog over the weekend, I can across an ancient post by Patrick Walton.

We had a fun discussion in #t-lang about possible new syntax for declaring functions in Rust.

One of the items on our Async 2027 Roadmap is to come up with some kind of asynchronous cleanup mechanism, like async Drop.

If you've been doing async for a while, you've probably heard someone say something like "the compiler takes an async function and converts it to a state machine."