Hacker News Reader

Comment by sizediterable | Hacker News Reader

In the first `async_std::task` example, we see that `JoinHandle::cancel` is an async function. I'm curious what would you do if you didn't care whether or not the cancellation succeeded and didn't want to await the cancellation. Would you wrap the cancellation in a task?

View on HN

The underlying implementation sets the task as cancelled the first time it is polled, and then waits for it to stop running [0]. So you could just call `cancel` and poll the future once:

    futures::poll!(task.cancel());

[0]: https://docs.rs/async-task/4.0.3/src/async_task/task.rs.html...

This seems to be for the `async-task` crate. My question was about `async_std::task` in particular since it doesn't have cancel-on-drop behavior.

async-std uses async-task under the hood.

(async-std -> async-global-executor -> async-executor -> async-task)

ah, makes sense!

Reply on news.ycombinator.com