Ben Smith

Yeah, maybe we should remove this repo? No one is updating it, and it is confusing when people find it and nothing works.

> That said though, tests written in wat directly, and targeting WASI APIs directly, are often very verbose and difficult to maintain, so it'd be good to collect compiled tests...

@devsnek that makes sense. It's a bit sad because those examples go from ~300 byte C files to ~30k wasm files. But I can definitely understand that the burden of...

Maybe the problem is that the `store` is the runtime global state for the VM, which doesn't really include execution. So exiting the store seems like the wrong terminology --...

As an alternative, we could make the instructions parameterized on the stack type when/if we add `v256` or other sizes. For example: `i32x4.add` currently has the signature `[v128 v128] ->...

Hm, so I can see this working for an offline tool, but how do you think we could make this work for a developer loading the wasm file from the...

I'm still having trouble seeing how this extra information would be used. The simplest thing is to say that all fields have to match exactly, but that is no better...

I like option 1 because I don't have to do anything :-) More than that though, option 2 would be kind of nasty to implement, since it will require reading...

It seems that it already does for object files, but we were seeing issues when generating assembly, then using the assembler to generate an object file.

It's not too hard to eyeball and spot an asm2wasm, wasm backend, rust, go etc. But this won't provide nearly as much info as the producer section will.