2020-08-29 19:35:41 +00:00
|
|
|
[package]
|
|
|
|
|
name = "bevy_tasks"
|
2022-11-12 20:01:29 +00:00
|
|
|
version = "0.9.0"
|
2021-10-27 00:12:14 +00:00
|
|
|
edition = "2021"
|
2020-11-03 21:34:00 +00:00
|
|
|
description = "A task executor for Bevy Engine"
|
|
|
|
|
homepage = "https://bevyengine.org"
|
|
|
|
|
repository = "https://github.com/bevyengine/bevy"
|
2021-07-23 21:11:51 +00:00
|
|
|
license = "MIT OR Apache-2.0"
|
2020-11-03 21:34:00 +00:00
|
|
|
keywords = ["bevy"]
|
2020-08-29 19:35:41 +00:00
|
|
|
|
|
|
|
|
[dependencies]
|
2020-09-10 19:54:24 +00:00
|
|
|
futures-lite = "1.4.0"
|
2020-09-20 18:27:24 +00:00
|
|
|
async-executor = "1.3.0"
|
2020-09-09 20:12:50 +00:00
|
|
|
async-channel = "1.4.2"
|
2022-11-07 21:43:07 +00:00
|
|
|
async-task = "4.2.0"
|
Add global init and get accessors for all newtyped TaskPools (#2250)
Right now, a direct reference to the target TaskPool is required to launch tasks on the pools, despite the three newtyped pools (AsyncComputeTaskPool, ComputeTaskPool, and IoTaskPool) effectively acting as global instances. The need to pass a TaskPool reference adds notable friction to spawning subtasks within existing tasks. Possible use cases for this may include chaining tasks within the same pool like spawning separate send/receive I/O tasks after waiting on a network connection to be established, or allowing cross-pool dependent tasks like starting dependent multi-frame computations following a long I/O load.
Other task execution runtimes provide static access to spawning tasks (i.e. `tokio::spawn`), which is notably easier to use than the reference passing required by `bevy_tasks` right now.
This PR makes does the following:
* Adds `*TaskPool::init` which initializes a `OnceCell`'ed with a provided TaskPool. Failing if the pool has already been initialized.
* Adds `*TaskPool::get` which fetches the initialized global pool of the respective type or panics. This generally should not be an issue in normal Bevy use, as the pools are initialized before they are accessed.
* Updated default task pool initialization to either pull the global handles and save them as resources, or if they are already initialized, pull the a cloned global handle as the resource.
This should make it notably easier to build more complex task hierarchies for dependent tasks. It should also make writing bevy-adjacent, but not strictly bevy-only plugin crates easier, as the global pools ensure it's all running on the same threads.
One alternative considered is keeping a thread-local reference to the pool for all threads in each pool to enable the same `tokio::spawn` interface. This would spawn tasks on the same pool that a task is currently running in. However this potentially leads to potential footgun situations where long running blocking tasks run on `ComputeTaskPool`.
2022-06-09 02:43:24 +00:00
|
|
|
once_cell = "1.7"
|
2022-12-13 21:00:43 +00:00
|
|
|
concurrent-queue = "2.0.0"
|
2021-07-14 20:52:50 +00:00
|
|
|
|
2020-09-25 22:26:23 +00:00
|
|
|
[target.'cfg(target_arch = "wasm32")'.dependencies]
|
|
|
|
|
wasm-bindgen-futures = "0.4"
|
2021-07-14 20:52:50 +00:00
|
|
|
|
|
|
|
|
[dev-dependencies]
|
|
|
|
|
instant = { version = "0.1", features = ["wasm-bindgen"] }
|
