Open Friz64 opened 1 week ago
That because single_threaded_task_pool::TaskPool::spawn returns FakeTask which can't contain future result, because it's just empty struct, but actualy for non wasm (for wasm it indeed can't do better, because uses wasm spawn method which allows only futures which outputs only empty tuple) it spawns future, gets it's task, waits while executor finishes, and return nothing (FakeTask), throwing away _task with result! I think should be two spawn
implementations for wasm (returning empty FakeTask) and for non-wasm which would return ready result T.
Bevy version
Any version after #13693
What you did
Compiled bevy without the
multi_threaded
feature, but with thesysinfo_plugin
featureWhat went wrong