wasmtime / issue #10620 Stabilize output of wasmtime-cli ... · git-wasmtime

Stream: git-wasmtime

Topic: wasmtime / issue #10620 Stabilize output of wasmtime-cli ...

Wasmtime GitHub notifications bot (Apr 21 2025 at 16:47):

Feature

Since earlier than 2019 (when the git blame shows we switched from docopt to structopt), wasmtime-cli's run --invoke flag has emitted the warning:
warning: using `--invoke` with a function that returns values is experimental and may break in the future
Now that we have invoke for components (#10054), and in general the Component Model has supplanted bare modules as the venue in which we expect to specify semantic extensions Wasm, I think we can get rid of this warning for modules. We should change the text of the warning for components to indicate that the wave text format may be unstable, since that is early enough in development and use that we don't want to guarantee stability there forever.

Alternatives

Do nothing - leave module invoke unstable forever. Its a niche feature which is of pretty limited use.

Wasmtime GitHub notifications bot (Apr 21 2025 at 21:17):

alexcrichton commented on issue #10620:

I was also thinking recently that we should remove these warnings since I'm not sure how we'd change the output or input in the future.

One note was that --invoke foo works for core modules but it's --invoke 'foo()' for components which is a bit weird, but also not the end of the world.

Wasmtime GitHub notifications bot (Apr 22 2025 at 12:13):

tschneidereit commented on issue #10620:

I agree that this seems fine to stabilize—perhaps after addressing the inconsistency Alex mentioned. I also just filed #10637 with a sketch for something more fundamental, but in the meantime this seems great to land.

Last updated: Dec 06 2025 at 06:05 UTC