Yeah we should get that over the line. @lukasa.hachyderm.io.ap.brid.gy is working on all the strict concurrency adoption in NIO right now.

Yes a third one is setting a task cancellation handler. Throwing a CancellationError is really just one way of indicating that something got cancelled but returning early is also totally fine.