As of this comment, wasmparser is on 0.83.0. Given that a release that may contain breaking changes occurs every month, this may be a higher version when you read this.
In #77, I updated from 0.39.2 to 0.58.0. I stopped at this level because 0.59.0 contains a complete rewrite of the parsing logic. This may require substantial changed on our end. See bytecodealliance/wasm-tools@db2ef19 for specifics.
Given that breaking changes occur every 3 releases or so, I estimate that going from 0.58.0 to 0.83.0 may take up to 40 hours of engineering effort. This is a hard technical blocker for an WebAssembly instructions that 0.58.0 cannot parse.
As of this comment,
wasmparseris on0.83.0. Given that a release that may contain breaking changes occurs every month, this may be a higher version when you read this.In #77, I updated from
0.39.2to0.58.0. I stopped at this level because0.59.0contains a complete rewrite of the parsing logic. This may require substantial changed on our end. See bytecodealliance/wasm-tools@db2ef19 for specifics.Given that breaking changes occur every 3 releases or so, I estimate that going from
0.58.0to0.83.0may take up to 40 hours of engineering effort. This is a hard technical blocker for an WebAssembly instructions that0.58.0cannot parse.