The promise of Async Rust often clashes with its current reality. This article argues that despite its potential, Async Rust remains in an MVP state, creating a 'two-tiered ecosystem' for developers. It highlights how Tokio's monoculture and the `Send + 'static` trap introduce significant complexity and overhead, often making traditional threading a more ergonomic and performant choice for common…

https://www.tpp.blog/aa12hwm

#programming #rust #asyncrust

🤖 This post was AI-generated.

🚀 Async Rust: the eternal MVP, where dreams of a supercharged compiler go to die. 🤣 But hey, let's keep writing "executor agnostic" code while waiting for the real magic to happen. 🪄✨
https://tweedegolf.nl/en/blog/237/async-rust-never-left-the-mvp-state #AsyncRust #superchargedCompiler #executorAgnostic #codeMagic #HackerNews #ngated
Async Rust never left the MVP state - Blog - Tweede golf

I've previously explained async bloat and some work-arounds for it, but would much prefer to solve the issue at the root, in the compiler. I've submitted a Project Goal, and am looking for help to ...

Async Rust never left the MVP state - Blog - Tweede golf

I've previously explained async bloat and some work-arounds for it, but would much prefer to solve the issue at the root, in the compiler. I've submitted a Project Goal, and am looking for help to ...

@rustaceans

Tokio!

It's 'static + multithreaded-by-default requirement has created the myth that async #Rust is inherently difficult.

People should use `smol` more - here's why:

#Async Rust can be a pleasure to work with (without `Send + Sync + 'static`) - by Evan Schwartz:

https://emschwartz.me/async-rust-can-be-a-pleasure-to-work-with-without-send-sync-static/

https://floss.social/@janriemer/114681713674697800

#smol #RustLang #Asynchronous #AsyncRust

The Evolution of Async Rust: From Tokio to High-Level Applications | The RustRover Blog

Tokio has become the de facto asynchronous runtime for high-performance networking in Rust, powering everything from backend services to databases. During the discussion, they explored how async Rust matured over the years, the architectural decisions behind Tokio, common challenges developers face today, and where the ecosystem is heading next.

The JetBrains Blog
🚀✨ RustConf 2025: where we learn that "cancelling" async Rust is as easy as cancelling your gym membership—good luck with that! The article promises a thrilling ride through the labyrinth of #programming jargon, complete with links nobody asked for and slides only a mother could love. 🎢🗣️
https://sunshowers.io/posts/cancelling-async-rust/ #RustConf2025 #asyncRust #humor #techcommunity #HackerNews #ngated
Cancelling async Rust · sunshowers

Correctness in the face of cancellations: a written version of my talk at RustConf 2025.

Cancelling async Rust

Ok, @calisti, I _think_, I've figured it out now (please read until the later parts of the toots as they are the most important)!🤓

Tldr; The `or` or `race` operators _on their own_ are not suitable for cancelling streams! One needs a `StopToken` or enum value _within the stream_ that signals cancellation/allows for short-circuiting.

1/?

#Rust #RustLang #AsyncRust #Async

Hey #Rust,

how dare you look so elegant as a systems programming language! 💅

#Smol #AsyncRust #RustLang

Second: Pinning helpers!

When doing async #Rust, there will be a point, where you'll get the ominous "Doesn't implement Unpin" error and "You need to pin your value".

First, learn about Pinning:
https://doc.rust-lang.org/std/pin/

Like, _really_ learn and understand it:
https://fasterthanli.me/articles/pin-and-suffering

And then use smol's pin! macro and the `pin_project` crate:
https://docs.rs/pin-project/latest/pin_project/

I might continue this thread with more insights I gain during this little project - stay tuned! 🙂

4/4?

#RustLang #AsyncRust

std::pin - Rust

Types that pin data to a location in memory.