| commit | 01c37e39341e1b7eea01901ff2b4204d4f5e4bd7 | [log] [tgz] |
|---|---|---|
| author | David Brazdil <[email protected]> | Tue Jan 24 18:05:05 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Jan 24 18:05:05 2023 +0000 |
| tree | 354b463f10d4a064dd5bf0561f5ba3da548210f1 | |
| parent | 7e4ae427a170c6085f7ee38d2b9ad1141f711c36 [diff] | |
| parent | 8304cf8ade605122abc0c6d505b5b904687ef1dc [diff] |
Update TEST_MAPPING am: 72f0890b13 am: 8304cf8ade Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/async-task/+/2398957 Change-Id: I3c877b61eb37579e8b6ec58d6e594e2c85604293 Signed-off-by: Automerger Merge Worker <[email protected]>
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.
Licensed under either of
at your option.
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.