History

BeastLe9enD ed3ecda91d Add `is_finished` to `Task<T>` (#6444 ) # Objective In some scenarios it can be useful to check if a task has been finished without polling it. I added a function called `is_finished` to check if a task has been finished. ## Solution Since `async_task` supports it out of the box, it is just a simple wrapper function. ---		2022-11-02 12:27:22 +00:00
..
examples	small and mostly pointless refactoring (#2934 )	2022-02-13 22:33:55 +00:00
src	Add `is_finished` to `Task<T>` (#6444 )	2022-11-02 12:27:22 +00:00
Cargo.toml	Nested spawns on scope (#4466 )	2022-09-28 01:59:10 +00:00
README.md	Cleanup of Markdown Files and add CI Checking (#1463 )	2021-02-22 04:50:05 +00:00

README.md

bevy_tasks

A refreshingly simple task executor for bevy. :)

This is a simple threadpool with minimal dependencies. The main usecase is a scoped fork-join, i.e. spawning tasks from a single thread and having that thread await the completion of those tasks. This is intended specifically for bevy as a lighter alternative to rayon for this specific usecase. There are also utilities for generating the tasks from a slice of data. This library is intended for games and makes no attempt to ensure fairness or ordering of spawned tasks.

It is based on async-executor, a lightweight executor that allows the end user to manage their own threads. async-executor is based on async-task, a core piece of async-std.

Dependencies

A very small dependency list is a key feature of this module

├── async-executor
│   ├── async-task
│   ├── concurrent-queue
│   │   └── cache-padded
│   └── fastrand
├── num_cpus
│   └── libc
├── parking
└── futures-lite