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
Protect wasm-smith against arbitrary Config differently (#1825)
* Protect wasm-smith against arbitrary `Config` differently
Currently `Arbitrary for Config` will perform some internal validation
of options, such as if reference-types are disabled then gc is also
disabled. This validation doesn't happen for other sources of `Config`
though, such as CLI options or from manual configuration. This commit
moves these checks from `Arbitrary for Config` to unconditionally
happening during module creation. This fixes a panic where if reference
types are disabled but tables are allowed then an internal assertion was
tripped because GC types were used when they shouldn't be.
* Add documentation
0 commit comments