Closed pchickey closed 1 week ago
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.
[ ] If you added a new Config
method, or modified an existing one, you
ensured that this configuration is exercised by the fuzz targets.
[ ] 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.
.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.](https://github.com/bytecodealliance/label-messager-action)
I noticed that the wasm_memory64 flag was left out of Config's debug impl, so rather than add it, I decided to use the
bitflags::Flags::FLAGS
const to iterate the complete set of flags.THe downside of this change is that it will print flags which do not have a setter in Config, e.g.
wasm_component_model_nested_names
.An alternative to this change is, rather than expanding out the single
features: WasmFeatures
member into many different debug_struct fields, the debug impl of WasmFeatures is used.Here is a sample debug of Config with this change: