Stream: git-wasmtime

Topic: wasmtime / issue #11224 Rework `component-model-async` AP...


view this post on Zulip Wasmtime GitHub notifications bot (Jul 11 2025 at 17:59):

dicej opened issue #11224:

Alex and I had a discussion and hack session today and came up with more ergonomic, harder to misuse, and easier-to-implement-efficiently APIs for e.g. TypedFunc::call_concurrent, StreamReader::read, etc. based on a refined version of the Accessor API we created for host functions. Early experiments show that we can adopt those APIs without major refactoring of the runtime internals; later, we can update the internals to take advantage of the efficiencies those new APIs unlock.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 11 2025 at 17:59):

dicej added the wasm-proposal:component-model-async label to Issue #11224.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 11 2025 at 18:00):

dicej assigned dicej to issue #11224.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 14 2025 at 17:16):

alexcrichton assigned alexcrichton to issue #11224.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 14 2025 at 17:16):

alexcrichton unassigned dicej from issue #11224.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 16 2025 at 22:11):

alexcrichton closed issue #11224:

Alex and I had a discussion and hack session today and came up with more ergonomic, harder to misuse, and easier-to-implement-efficiently APIs for e.g. TypedFunc::call_concurrent, StreamReader::read, etc. based on a refined version of the Accessor API we created for host functions. Early experiments show that we can adopt those APIs without major refactoring of the runtime internals; later, we can update the internals to take advantage of the efficiencies those new APIs unlock.


Last updated: Dec 06 2025 at 07:03 UTC