JF Bastien

@binji > For filesystems I think we would follow the way it was done in emscripten + NaCl and have the ability to mount different filesystems on the same hierarchy....

http://webassembly.org/docs/faq/ ? I wouldn't have two places for frequently asked questions. Organizing them is good though.

Great start, ty. I may take a stab at more later.

How would this interact with ES6 module integration? /cc @linclark

I'd explore two possibilities for multiple memories: 1. Specified as an immediate on a memory access. This is what LLVM has in its IR. 2. Specified as a variable value...

> Agreed on wanting both immediate [linear memory index](https://github.com/WebAssembly/design/blob/master/Modules.md#linear-memory-index-space) and, later, first-class `Memory` GC reference types. To avoid adding a whole duplicate classes of opcodes, what I've been assuming is...

>> reference (in which case the operator's signature gains a Memory operand). > > If we did this, that would be the first instance where you can't just look at...

> My point was that the reference form would change the values popped from the operand stack depending on the operator's immediates. I mistakenly thought that would be the first...

FWIW we don't apply all the limits because some didn't make sense to our implementation. The ones we apply are here: https://github.com/WebKit/webkit/blob/master/Source/JavaScriptCore/wasm/WasmLimits.h In particular, I dropped function size because it's...