> There isn't a technical reason for why Rust couldn't do this. First, it would be a huge undertaking. That in itself is a huge time/resource burden. Second,

> There isn't a technical reason for why Rust couldn't do this. First, it would be a huge undertaking. That in itself is a huge time/resource burden. Second, it would add overhead to any non-async function call. Because async introduces branching on every function invocation, it would make the resulting assembly even harder to understand. This strongly goes against the zero overhead/ zero cost abstraction idea of Rust. By the same measure, Go could technically remove (almost) all GC, add some kind of borrowing mechanism and steal Rust's thunder.