> e.g. Linux mutexes You don't want to use blocking mutexes anyway with async. > or Rust's Rc This is only half true. The danger is that two `Rc` that point

> e.g. Linux mutexes You don't want to use blocking mutexes anyway with async. > or Rust's Rc This is only half true. The danger is that two `Rc` that point to the same data are in different threads. But it should be safe to move all of them at once from one thread to another, which is exactly the case if all the `Rc`s involved live inside a `Future`. The problem is that this is a non-local property that's hard to encode in the type system. > By the way, if you wish to test uncolored async in Rust, you can find an implementation here: https://github.com/Xudong-Huang/may https://github.com/Xudong-Huang/may . FYI that's known to be unsound due to thread locals. And more generally it doesn't seem to give much attention to safety (see for example how it allowed unsound scoped tasks, or the fact it allows doing unsafe operations in some of its macros due to wrong scoping of `unsafe` blocks).