-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Component
for WASM FakeTask
#4052
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bonk
That is, we shouldn't be implementing Component
for Task
at all.
#2982 already would remove the other wrong impl, and that part of the pr is afaik entirely non-controversial.
I agree, neither |
Closing this out, following the direction taken in #2982. |
# Objective - `Task` are `Component`. - They should not. ## Solution - Remove the impl, and update the example to show a wrapper. #4052 for reference
# Objective - `Task` are `Component`. - They should not. ## Solution - Remove the impl, and update the example to show a wrapper. bevyengine#4052 for reference
# Objective - `Task` are `Component`. - They should not. ## Solution - Remove the impl, and update the example to show a wrapper. bevyengine#4052 for reference
Objective
Although in the WASM case, there is no result in the task future's output. Instead, it provides a
detach()
function.Solution
Task
, implementComponent
forFakeTask
on the wasm32 target.