No, stackful coroutines requires a runtime. Not going to work on embedded, which is where async rust shines the strongest.

If you don't care about embedded that is fine. But almost all systems in the world are embedded. "Normal" computers are the odd ones out. Every "normal" computer has several embedded systems in it (one or more of SSD controller, NIC, WiFi controller, celular modem, embedded controller, etc). And then cars, appliances, cameras, routers, toys, etc have many more.

It is a use case that matters. To have secure and reliable embedded systems is important to humanity's future. We need to turn the trend of major security vulnerabilities and buggy software in general around. Rust is part of that story.

> You can do basically the same thing with stackfull coroutines.

...Minus the various tradeoffs that made stackful coroutines a nonstarter for Rust's priorities. For example, Rust wanted:

- Tight control over memory use (no required heap allocation, so segmented stacks are out)

- No runtime (so no stack copying and/or pointer rewriting)

- Transparent/zero-cost interop over C FFI (i.e., no need to copy a coroutine stack to something C-compatible when calling out to FFI)

> You can do basically the same thing with stackfull coroutines.

It's clear that you don't understand the use cases that async in Rust was designed to accommodate.

> Also the ecosystem is setup so you have to use tokio and everything has to be an Arc.

It's clear that you're not at all familiar with the Rust async ecosystem, including Embassy.