Add runtime::spawn for WASIp3 - #156
Conversation
aed32e0 to
85c8252
Compare
| }); | ||
| }); | ||
| runnable.schedule(); | ||
| task |
There was a problem hiding this comment.
I'm a little disappointed that wasip3::spawn_local can't return a handle, and I haven't explored why we can't add that in wit-bindgen, but I assume thats a problem too big to solve right now. My biggest concern here is that if we're relying on the CM task's context to take care of disambiguating context at the host (i.e. the CDN-Loop problem), we need the not-yet-existing guest functionality for getting and setting task context.
I guess we have to roll with this because its the only way for now? But lets also make sure we follow up on the task context set/get soon.
There was a problem hiding this comment.
I made the change to have spawn_local return a handle already here: bytecodealliance/wit-bindgen#1710 (comment) , so we can switch to that in a follow up after both wit-bindgen and wasip3 are released. But yes we should also still follow up on the context get/set separately.
2 participants
Implements
spawnfor the WASIp3 target.Resolves #152