Ben Smith

I thought that we were preventing circular dependencies by preventing defined globals from using referencing non-imported globals in their init expression, and mutability was orthogonal. In any case, another thing...

> [To wit, lest anyone else be initially confused, reading the validation rules for init expressions suggests that any (imported or defined) const global can be used, however, module validation...

> One could argue that since this is a number value the implicit mutability specifier is const, but need it be so? It makes the most sense to me for...

WebAssembly doesn't have an `i16` value type, so that instruction wouldn't be useful. Instead, you can use `i32.extend8_s` followed by `i32.store16` to write a 16-bit value to linear memory.

16-bit floating point support is mentioned as a future feature [here](https://github.com/WebAssembly/design/blob/master/FutureFeatures.md#16-bit-and-128-bit-floating-point-support). 16-bit integer value types are less useful, in my opinion.

> I have a modest proposal that is perhaps more relevant to other in-development features than to this one. It is that we not mix test cases for in-development features...

> It makes me think that we didn't understand the limit correctly. According to v8/module-decoder.cc, it looks like it is checking the size in bytes. Unfortunately, it looks like `DecodeWasmFunction`...

It might be nice to have some more information about the largest functions we've seen before making this choice.

Oh man, I can't believe I missed this. Thanks for reporting! I've pushed a fix, but haven't pushed a new release yet. Have you found any other issues?

Hey, thanks for the great feedback! I'll take a look at fixing these things soon. > May i ask why are there inaccuracies, isn't porklike open source? Sort of, the...