@janriemer Am I stupid or is this sync-over-async literally how 99% of software is written in every single language that supports async? 🧐

@janriemer vs-threading has utils for mixing sync and async and analyzers for the common pitfalls.

https://github.com/microsoft/vs-threading

I think c# has an awkward async implementation cause of its obsession with backward compatibility (async void?) and cause it was one of the first languages using the pattern.(it's not clear what is running single threaded with continuations and what on a thread pool)

Afaik (please correct me if I'm wrong), Async Rust doesn't have this problem of deadlocking (deadlocks do occur in other scenarios, like holding a sync Mutex over an await, though):

The main thread calls `block_on`. Within `block_on` a Future is scheduled by a _dedicated_ runtime (at least this is the case with Tokio).
When scheduling a potential blocking task within an async context, one uses `spawn_blocking`, which spawns tasks on a dedicated thread pool.

My conclusion is pending...😄

2/?