Sure, the situation is just vastly better - even now - than standardizing the wrong solution. Each widely used async runtime in Rust has different solutions for

Sure, the situation is just vastly better - even now - than standardizing the wrong solution. Each widely used async runtime in Rust has different solutions for a number of problems, and the choice isn't obvious. For example, `tokio::spawn()` returns a task handle that lets the task keep running after the handle is dropped. `smol::spawn()` cancels the task when the task handle is dropped. General async cancellation requires infrastructure mechanisms, and there are multiple reasonable designs. Letting things settle in the ecosystem is a great way to find the best design to eventually incorporate in the standard library, but it takes time.