Skip to content

implement {future,stream}.forward - #14206

Draft
rvolosatovs wants to merge 1 commit into
bytecodealliance:mainfrom
rvolosatovs:stream-future-forward
Draft

rvolosatovs wants to merge 1 commit 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#717

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

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

@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
Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
@rvolosatovs
rvolosatovs force-pushed the stream-future-forward branch from 1b4f01f to fc69687 Compare October 5, 2026 16:23
@github-actions github-actions Bot added fuzzing Issues related to our fuzzing infrastructure wasmtime:c-api Issues pertaining to the C API. wasmtime:config Issues related to the configuration of Wasmtime labels Oct 5, 2026
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

Subscribe to Label Action

cc @fitzgen

Details This issue or pull request has been labeled: "fuzzing", "wasm-proposal:component-model-async", "wasmtime:api", "wasmtime:c-api", "wasmtime:config"

Thus the following users have been cc'd because of the following labels:

  • fitzgen: fuzzing

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

Label Messager: wasmtime:config

It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:

  • If you added a new Config method, you wrote extensive documentation for
    it.

    Details

    Our documentation should be of the following form:

    Short, simple summary sentence.
    
    More details. These details can be multiple paragraphs. There should be
    information about not just the method, but its parameters and results as
    well.
    
    Is this method fallible? If so, when can it return an error?
    
    Can this method panic? If so, when does it panic?
    
    # Example
    
    Optional example here.
    
  • If you added a new Config method, or modified an existing one, you
    ensured that this configuration is exercised by the fuzz targets.

    Details

    For example, if you expose a new strategy for allocating the next instance
    slot inside the pooling allocator, you should ensure that at least one of our
    fuzz targets exercises that new strategy.

    Often, all that is required of you is to ensure that there is a knob for this
    configuration option in wasmtime_fuzzing::Config (or one
    of its nested structs).

    Rarely, this may require authoring a new fuzz target to specifically test this
    configuration. See our docs on fuzzing for more details.

  • If you are enabling a configuration option by default, make sure that it
    has been fuzzed for at least two weeks before turning it on by default.


Details

To modify this label's message, edit the .github/label-messager/wasmtime-config.md file.

To add new label messages or remove existing label messages, edit the
.github/label-messager.json configuration file.

Learn more.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fuzzing Issues related to our fuzzing infrastructure 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 wasmtime:c-api Issues pertaining to the C API. wasmtime:config Issues related to the configuration of Wasmtime

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants