You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of the component model async implementation work involves adding support to wasmtime-cranelift for intrinsic functions such as task.return, stream.new, etc. Although we expect those intrinsics to normally only be called by Wasm code, it's possible that a module could directly export its import of a given intrinsic, allowing the host to call it directly. In that case, we need to support the array ABI.
As of this writing, not enough async support has been merged into main to test such a scenario, but we should test and support it once we are able to.
Part of the component model async implementation work involves adding support to
wasmtime-cranelift
for intrinsic functions such astask.return
,stream.new
, etc. Although we expect those intrinsics to normally only be called by Wasm code, it's possible that a module could directly export its import of a given intrinsic, allowing the host to call it directly. In that case, we need to support the array ABI.As of this writing, not enough async support has been merged into main to test such a scenario, but we should test and support it once we are able to.
See #10106 (comment) for details.
The text was updated successfully, but these errors were encountered: