Sven Sauleau

We should also figure out how to represent those? (you are the float expert here), for example: `(f32.const nan:0x200000)` could be represented as: ```js FloatLiteral = { type: 'FloatLiteral', value:...

Unfortunately the interpreter wasn't a priority for us but we already have a couple of spec tests passing, see https://github.com/xtuc/webassemblyjs/blob/21f3f76be512f5391826311d36e8b3575d6ce014/Makefile#L45 It's not complete but in a good shape.

Yes, we have a few inconsistencies. The switch to the Web IDL spec also introduced more of them.

Btw here's a PR https://github.com/xtuc/webassemblyjs/pull/338, i'm currently working on it

I just merged https://github.com/xtuc/webassemblyjs/pull/449, branching and control flow should be easier now.

I just to reproduce and got a different error: ``` /tmp/31161/node_modules/@webassemblyjs/wast-parser/lib/grammar.js:80 throw new Error("\n" + (0, _helperCodeFrame.codeFrameFromSource)(source, token.loc) + "Assertion error: expected token of type " + type + ",...

Could you please send me the Wasm module, if you can? > [...] pass a i64 param to a function This is not possible yet, there's ongoing work to support...

Thanks, I'll investigate that during the holidays. The article I wrote is about the native support which is not yet deployed widely. I know that we have a hack to...

With https://github.com/xtuc/webassemblyjs/pull/473 merged I'm down to two errors: ``` Validation errors: Expected type i64 but got i32 at func_21:123. Stack contains additional type i32 at func_35. ```

Thanks, you too and see in at D2 :smiley: