Module bevy_internal::tasks
source · Expand description
Pools for async, IO, and compute tasks.
Modules§
- Futures, streams, and async I/O combinators.
Structs§
- A newtype for a task pool for CPU-intensive work that may span across multiple frames
- A newtype for a task pool for CPU-intensive work that must be completed to deliver the next frame
- An empty task used in single-threaded contexts.
- A newtype for a task pool for IO-intensive work (i.e. tasks that spend very little time in a “woken” state)
- A
TaskPool
scope for running one or more non-'static
futures. - Wraps
async_executor::Task
, a spawned future. - A thread pool for executing tasks. Tasks are futures that are being automatically driven by the pool on threads owned by the pool. In this case - main thread only.
- Used to create a
TaskPool
. - This is a dummy struct for wasm support to provide the same api as with the multithreaded task pool. In the case of the multithreaded task pool this struct is used to spawn tasks on a specific thread. But the wasm task pool just calls
wasm_bindgen_futures::spawn_local
for spawning which just runs tasks on the main thread and so theThreadExecutor
does nothing.
Traits§
ParallelIterator
closely emulates thestd::iter::Iterator
interface. However, it usesbevy_task
to compute batches in parallel.- Provides functions for mapping read-only slices across a provided
TaskPool
. - Provides functions for mapping mutable slices across a provided
TaskPool
.
Functions§
- Gets the logical CPU core count available to the current process.
- Blocks the current thread on a future.
- Polls a future just once and returns an
Option
with the result. - A function used by
bevy_core
to tick the global tasks pools on the main thread. This will run a maximum of 100 local tasks per executor per call to this function.