wasmparser
Advanced tools
Changelog
2.0.0 (2020-06-10)
The type section can be reconstructed from the implicit type information in the remainder of the disassembly, and is generally just cognitive overhead for developers, especially in the browser DevTools (see https://crbug.com/1092763 for relevant downstream issue in Chromium DevTools). Relying on the implicit type information is far more readable for humans and also avoids the need to dump all the types in the beginning, which take up precious space since both Chromium and Firefox DevTools limit the number of lines that are displayed for large Wasm modules.
This adds a skipTypes
option to WasmDisassembler
instances, which
can be used to restore the old behavior. By default this option is set
to true
.
This includes a fix to call_indirect
and return_call_indirect
,
where we had previously refered to the type by name, and now we
use the abbreviated form for printing types as well [1].
Changelog
2.0.0 (2020-06-10)
The type section can be reconstructed from the implicit type information in the remainder of the disassembly, and is generally just cognitive overhead for developers, especially in the browser DevTools (see https://crbug.com/1092763 for relevant downstream issue in Chromium DevTools). Relying on the implicit type information is far more readable for humans and also avoids the need to dump all the types in the beginning, which take up precious space since both Chromium and Firefox DevTools limit the number of lines that are displayed for large Wasm modules.
This adds a skipTypes
option to WasmDisassembler
instances, which
can be used to restore the old behavior. By default this option is set
to true
.
This includes a fix to call_indirect
and return_call_indirect
,
where we had previously refered to the type by name, and now we
use the abbreviated form for printing types as well [1].