You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 29, 2025. It is now read-only.
Currently, if WasmTransformer or the SwiftWasm toolchain produce invalid binaries, our users can only discover this when loading the binary in a Wasm host (the browser in most cases). We should detect invalid binaries earlier for better user experience.
In certain cases some of the transformations (I64ImportTransformer for example) can produce invalid binaries. Of course such transformations should be fixed in the first place to avoid this, but I think it would be better long-term to have a validation pass built-in for better diagnostics.
Currently, if
WasmTransformeror the SwiftWasm toolchain produce invalid binaries, our users can only discover this when loading the binary in a Wasm host (the browser in most cases). We should detect invalid binaries earlier for better user experience.In certain cases some of the transformations (
I64ImportTransformerfor example) can produce invalid binaries. Of course such transformations should be fixed in the first place to avoid this, but I think it would be better long-term to have a validation pass built-in for better diagnostics.