Sven Sauleau
Sven Sauleau
You can deactivate the check: https://github.com/xtuc/webassemblyjs/blob/master/packages/repl/src/index.js#L299-L307 We are testing i64 in the spectest via our REPL.
I believe this types are used by webpack, if we rename the file we need to ensure webpack doesn't break. Would you mind sending a PR?
Long term I think we should remove flow in the repo and replace with typescript.
Hi @TimHambourger, thanks for your bug reports (and the great test suite, do you mind if we use it?). This issue is due to a design bug. Here's the definition...
Yes, that's right, for example a ModuleExport would have an index and optionnally a name. We can then use the information we need depending on what we do.
The `decode` is exported by `@webassemblyjs/wasm-parser`, but it looks like nodejs requires file to be .mjs. Could you please send a change to rename the files?
@Chehx what is the parse failure you are seeing?
Following our discussion on Slack. I would suggest adding a transformation that flatten the AST before the Module compilation (like the identifier ⟶ index transformation). That would allow different representation...
I have mixed feelings on that. Here are a few points: - Locals can only be before any instructions in a func body. - Allocation is done by going through...
Ok that's a good point. Here the code handling the locals in the interpreter: https://github.com/xtuc/webassemblyjs/blob/master/packages/webassemblyjs/src/interpreter/kernel/exec.js#L693-L698 Quick clarification, function locals end up in stackframe locals. We pass the params of the...