The problem has been known from the beginning, because async I/O on Windows has the same issues as io_uring. Rust went with poll-based API and synchronous canc

The problem has been known from the beginning, because async I/O on Windows has the same issues as io_uring. Rust went with poll-based API and synchronous cancellation design anyway, because that fits ownership and borrowing. Making async cancellation work safely even in presence of memory leaks (destructors don't always run) and panics remains an unsolved design problem.