Yes it's VERY important to differenciate between async/await support (co-rutine) and doing async-io. The problems all come from async-io. "Pure" async/await c

Yes it's VERY important to differenciate between async/await support (co-rutine) and doing async-io. The problems all come from async-io. "Pure" async/await can be mixed and matched in rust without any problems. But the moment you touch IO (including timeout) a reactor is needed and things get complicated.