Andreas Rossberg

That seems to be an oversight. It should probably have been changed in the same way as test/run.py back when SIMD tests where written or merged. I don't know who...

That seems to be an oversight. It should probably have been changed in the same way as test/run.py back when SIMD tests where written or merged. I don't know who...

I'd also have a preference for removing the exception.

Agreed with @ajklein. I think for the no-frills approach the appropriate cause of action for type reflection would be not to add anything complex yet. We should even drop the...

Yes, we definitely should not "weaken" non-expressible types. If something isn't any/func/externref, you cannot reflect it, i.e., the respective .type functions would throw for now. Everything else would not be...

@manoskouk, yes, those are different types, that's a direct consequence of the iso-recursive semantics. As long as the JS API has no syntax for recursive types, it can only create...

I think we should keep them consistent. It actually simplifies some formulations as well when we have a named phrase like `ext ::= FINAL | OPEN`, because then `ext` can...

@tlively, I can try, but I can't promise anything — I'm on an a flight Odyssee right now after I was dumped from my flight back to Europe yesterday. Hence...

Sorry, I had somehow missed this PR before the holidays. I agree that it looks like the original intention was that all failures in linking throw LinkError. Perhaps the most...

You won't usually be able to map Wasm arrays to language arrays directly, as they are more low-level. Most languages have (different) extra features that Wasm arrays do not have,...