Stream: git-wasmtime

Topic: wasmtime / issue #11600 Expose when component model async...


view this post on Zulip Wasmtime GitHub notifications bot (Sep 03 2025 at 18:57):

alexcrichton opened issue #11600:

Today Func::call_concurrent will resolve when the guest invokes task.return, but the guest can continue running. This concept, supported by the component model, should be modeled in Wasmtime's embedder API as well. For example the return value of call_concurrent could always return a WasmTask argument (or something like that) which can then be used to await with an &Accessor just as a function could be called concurrently. This would enable the embedder to, optionally, explicitly wait on guests that would like to continue running. Additionally the embedder could learn about traps during this time frame, but no other results would come out of the guest.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 03 2025 at 18:57):

alexcrichton added the wasmtime:api label to Issue #11600.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 03 2025 at 18:57):

alexcrichton added the wasm-proposal:component-model-async label to Issue #11600.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 08 2025 at 22:44):

rvolosatovs commented on issue #11600:

This makes a lot of sense! As an embedder I would expect to be able to acquire a construct similar to https://docs.rs/tokio/latest/tokio/task/struct.JoinSet.html

view this post on Zulip Wasmtime GitHub notifications bot (Sep 09 2025 at 15:45):

alexcrichton assigned dicej to issue #11600.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 10 2025 at 20:49):

dicej closed issue #11600:

Today Func::call_concurrent will resolve when the guest invokes task.return, but the guest can continue running. This concept, supported by the component model, should be modeled in Wasmtime's embedder API as well. For example the return value of call_concurrent could always return a WasmTask argument (or something like that) which can then be used to await with an &Accessor just as a function could be called concurrently. This would enable the embedder to, optionally, explicitly wait on guests that would like to continue running. Additionally the embedder could learn about traps during this time frame, but no other results would come out of the guest.


Last updated: Dec 06 2025 at 07:03 UTC