We actively ban Rust's async /await syntax from our codebase for a few reasons, though primarily it's been an issue with it's lack of maturity. If feels incredibly painful to use in all but the most trivial cases. However; even if were to be much more user friendly, it still would be the wrong model for most of our code since we care significantly more about parallelism then about concurrency.

Having use async/await in production a bit, I wouldn't really recommend it to anybody: the async runtimes are large dependencies typically that are difficult to roll your own, understand or debug. Code built on top of them has numerous performance issues that I uncovered when running it through it's paces. Much as I'm a fan of Rust, a fan of async await, I am not.