-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the wasm-tools family of crates #8882
Update the wasm-tools family of crates #8882
Conversation
This notably brings in a limitation where component model flags types must have 32 or fewer flags in accordance with the transition plan of WebAssembly/component-model#370. A feature flag is added to go back to the previous behavior to avoid breaking anyone too much. This additionally brings in a fix for a panic when validating invalid modules with tail calls.
I'll note that this is a draft as I'd like to get in bytecodealliance/wit-bindgen#990 and bytecodealliance/wit-bindgen#989 and update wit-bindgen here too |
Ok should be reading pending CI |
3988753
to
2994075
Compare
On second thought let's not update wit-bindgen. |
Label Messager: wasmtime:configIt looks like you are changing Wasmtime's configuration options. Make sure to
To modify this label's message, edit the To add new label messages or remove existing label messages, edit the |
* Update the wasm-tools family of crates This notably brings in a limitation where component model flags types must have 32 or fewer flags in accordance with the transition plan of WebAssembly/component-model#370. A feature flag is added to go back to the previous behavior to avoid breaking anyone too much. This additionally brings in a fix for a panic when validating invalid modules with tail calls. * Add vet entries
* Update the wasm-tools family of crates This notably brings in a limitation where component model flags types must have 32 or fewer flags in accordance with the transition plan of WebAssembly/component-model#370. A feature flag is added to go back to the previous behavior to avoid breaking anyone too much. This additionally brings in a fix for a panic when validating invalid modules with tail calls. * Add vet entries
This notably brings in a limitation where component model flags types must have 32 or fewer flags in accordance with the transition plan of WebAssembly/component-model#370. A feature flag is added to go back to the previous behavior to avoid breaking anyone too much.
This additionally brings in a fix for a panic when validating invalid modules with tail calls.