ee15be8549
# Objective Right not bevy's task pool abstraction is kind of useless on wasm, since it returns a `FakeTask` which can't be interacted with. This is only good for fire-and-forget it tasks, and isn't even that useful since it's just a thin wrapper around `wasm-bindgen-futures::spawn_local` ## Solution Add a simple `Task<T>` handler type to wasm targets that allow waiting for a task's output or periodically checking for its completion. This PR aims to give the wasm version of these tasks feature parity with the native, multi-threaded version of the task ## Testing - Did you test these changes? *Not yet* --------- Co-authored-by: Periwink <charlesbour@gmail.com> Co-authored-by: Jan Hohenheim <jan@hohenheim.ch> |
||
|---|---|---|
| .. | ||
| iter | ||
| lib.rs | ||
| single_threaded_task_pool.rs | ||
| slice.rs | ||
| task_pool.rs | ||
| task.rs | ||
| thread_executor.rs | ||
| usages.rs | ||
| wasm_task.rs | ||