tag | ddd8176ec28c6b3be78021c6d161df5c6bff4c64 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Mon Apr 29 10:35:40 2024 -0700 |
object | 0106d6852f851fc78b3000167207f5cb791986b5 |
aml_tz3_314012070 (11568888,com.google.android.tzdata3)
commit | 0106d6852f851fc78b3000167207f5cb791986b5 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Jun 15 21:43:22 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Jun 15 21:43:22 2022 +0000 |
tree | a3acf4ff2edd7c51a897225a12fa5a5290aaa408 | |
parent | 835f0e9a6358179762c79c80ddcefd29ce1ce494 [diff] | |
parent | 3b9ccd1daed9870e484cf8921cf349713d62d11b [diff] |
Snap for 8730993 from 3b9ccd1daed9870e484cf8921cf349713d62d11b to mainline-tzdata3-release Change-Id: I315431be82572efffc6b09575b3b4e90d6e1a46f
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.