alexcrichton opened issue #14108:
This proposal has recently moved to stage 4 support in the CG meaning that modules may start using this by default. We should enable this within Wasmtime and turn it on as well. This won't really require any substantive changes to Wasmtime since the proposal is primarily implemented in
wasmparserwhich already implements this. The main change, though, is that we probably want to enable fuzzing for this proposal as it's not currently implemented.
alexcrichton added the enhancement label to Issue #14108.
chacailline commented on issue #14108:
Hi, I'd like to work on this.
It'll be my first PR, but I see #9403 looks similar. I think I need to:
- Add
wasm-smithgeneration for compact imports (it doesn't currently AFAICT), and enable it inwasmtimefuzzing config.- Follow implementation steps in the docs, and enable the feature by default.
Anything else?
chacailline edited a comment on issue #14108:
Hi, I'd like to work on this.
It'll be my first PR, but I see #9403 looks similar. I think I need to:
- Add
wasm-smithgeneration for compact imports (it doesn't currently AFAICT), and enable it inwasmtimefuzzing config.- Follow implementation steps in the docs, and enable the proposal by default.
Anything else?
alexcrichton commented on issue #14108:
That's about right yeah, and this'll be a bit easier than most since it has virtually no impact on Wasmtime outside of configuration. For example there's no API changes necessary.
These are the requirements for enabling a feature by default, so yeah I'd summarize the major missing pieces as (a) fuzzing and (b) configuration. For the configuration side that'd be things like a
Configmethod, a CLI flag, C API, etc. The docs you've found (online here as well) may be a little outdated, but if you'd like to update those along the way with any edits/steps you've done as well that'd be much appreciated!
Last updated: Aug 30 2026 at 09:07 UTC