Stream: git-wasmtime

Topic: wasmtime / issue #12166 component-model-async: validation...

Wasmtime GitHub notifications bot (Dec 15 2025 at 22:05):

lukewagner opened issue #12166:

According to these rules (canon stream.read (stream) (core func)) should validate without a memory immediate. (canon future.read (future) (core func)) successfully validates, so this seems specific to streams. .wast test will be forthcoming in CM/#580

Wasmtime GitHub notifications bot (Dec 15 2025 at 22:27):

lukewagner edited issue #12166:

According to these rules (canon stream.read (stream) (core func)) should validate without a memory immediate. (canon future.read (future) (core func)) successfully validates, so this seems specific to streams. Test added as test/async/same-component-stream-future.wast in CM repo (fails validation, should succeed).

Wasmtime GitHub notifications bot (Dec 18 2025 at 17:10):

fitzgen added the wasm-proposal:component-model-async label to Issue #12166.

Wasmtime GitHub notifications bot (Dec 18 2025 at 20:46):

dicej commented on issue #12166:

This should be addressed by https://github.com/bytecodealliance/wasm-tools/pull/2406

Wasmtime GitHub notifications bot (Dec 18 2025 at 21:00):

lukewagner commented on issue #12166:

Thanks! Happy to close this now if that's appropriate.

Wasmtime GitHub notifications bot (Dec 18 2025 at 21:02):

alexcrichton commented on issue #12166:

Oh we can take care of closing, but I'd like to leave this open until we update wasm-tools here to track that. I also think we'll want tests to ensure that wasmtime is ready for compilation/runtime if the memory option isn't present (I'd naively expect it to unwrap it today)

Wasmtime GitHub notifications bot (Dec 18 2025 at 21:09):

dicej commented on issue #12166:

I also think we'll want tests to ensure that wasmtime is ready for compilation/runtime if the memory option isn't present (I'd naively expect it to unwrap it today)

We might get lucky there since streams and futures share a lot of code, and the memory option has already been optional for futures for a while. We'll see.

Wasmtime GitHub notifications bot (Jan 08 2026 at 00:14):

alexcrichton closed issue #12166:

According to these rules (canon stream.read (stream) (core func)) should validate without a memory immediate. (canon future.read (future) (core func)) successfully validates, so this seems specific to streams. Test added as test/async/same-component-stream-future.wast in CM repo (fails validation, should succeed).

Wasmtime GitHub notifications bot (Jan 08 2026 at 00:14):

alexcrichton commented on issue #12166:

Updated/tested in https://github.com/bytecodealliance/wasmtime/pull/12254

Last updated: Jan 09 2026 at 13:15 UTC