Go to file
Stjepan Glavina b5ec84da08 Bump to v4.0.3 2020-10-19 00:05:35 +02:00
.github Don't let clippy fail the build 2020-05-11 12:23:20 +02:00
benches Docs and comments 2020-09-19 21:34:44 +02:00
examples More docs and small fixes 2020-09-20 02:12:51 +02:00
src Document the return value of run() 2020-10-19 00:05:09 +02:00
tests Fix tests 2020-09-20 02:24:41 +02:00
.gitignore Initial commit 2019-08-12 20:18:51 +02:00
CHANGELOG.md Bump to v4.0.3 2020-10-19 00:05:35 +02:00
Cargo.toml Bump to v4.0.3 2020-10-19 00:05:35 +02:00
LICENSE-APACHE Initial commit 2019-08-12 20:18:51 +02:00
LICENSE-MIT Initial commit 2019-08-12 20:18:51 +02:00
README.md Update readme 2020-09-19 21:53:38 +02:00

README.md

async-task

Build License Cargo Documentation

Task abstraction for building executors.

To spawn a future onto an executor, we first need to allocate it on the heap and keep some state attached to it. The state indicates whether the future is ready for polling, waiting to be woken up, or completed. Such a stateful future is called a task.

All executors have a queue that holds scheduled tasks:

let (sender, receiver) = flume::unbounded();

A task is created using either spawn(), spawn_local(), or spawn_unchecked() which return a Runnable and a Task:

// A future that will be spawned.
let future = async { 1 + 2 };

// A function that schedules the task when it gets woken up.
let schedule = move |runnable| sender.send(runnable).unwrap();

// Construct a task.
let (runnable, task) = async_task::spawn(future, schedule);

// Push the task into the queue by invoking its schedule function.
runnable.schedule();

The Runnable is used to poll the task's future, and the Task is used to await its output.

Finally, we need a loop that takes scheduled tasks from the queue and runs them:

for runnable in receiver {
    runnable.run();
}

Method run() polls the task's future once. Then, the Runnable vanishes and only reappears when its Waker wakes the task, thus scheduling it to be run again.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.