Skip to content

implement {future,stream}.forward - #14206

Draft
rvolosatovs wants to merge 2 commits into
bytecodealliance:mainfrom
rvolosatovs:stream-future-forward
Draft

implement {future,stream}.forward#14206
rvolosatovs wants to merge 2 commits into
bytecodealliance:mainfrom
rvolosatovs:stream-future-forward

Conversation

@rvolosatovs

@rvolosatovs rvolosatovs commented Aug 25, 2026

Copy link
Copy Markdown
Member

implement {future,stream}.forward as defined in WebAssembly/component-model#709

I have run the test suite from CM PR against this implementation, but I did not update the submodule, since there are a few test cases in the spec repo main, which Wasmtime currently fails.

The test cases are entirely LLM-generated, mostly based on the Python host tests in the spec (which are also LLM-generated)

The implementation is LLM-generated, but based on a rough sketch I wrote by hand.

Pick up `wasmparser`/`wast`/`wasm-encoder` support for the
`stream.forward` and `future.forward` canonical built-ins from
bytecodealliance/wasm-tools#2614 until that
lands upstream.
Signed-off-by: Roman Volosatovs <[email protected]>
@rvolosatovs
rvolosatovs force-pushed the stream-future-forward branch from 64da217 to 1b4f01f Compare August 25, 2026 18:08
@github-actions github-actions Bot added the wasmtime:api Related to the API of the `wasmtime` crate itself label Aug 25, 2026
@fitzgen fitzgen added the wasm-proposal:component-model-async Issues related to the WebAssembly Component Model async proposal label Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wasm-proposal:component-model-async Issues related to the WebAssembly Component Model async proposal wasmtime:api Related to the API of the `wasmtime` crate itself

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants