Andreas Rossberg

@littledan, well, it would be highly unfortunate to make the Wasm core spec dependent on JavaScript. Moreover, it seems rather unlikely that the memory primitives exposed by the JS model...

"Variable" strikes me as a bit too unspecific. I'd prefer "XYGlobal", for some nice choice of XY (so that we leave the door open to also add YZGlobals of the...

@titzer, but the "global" refers to the lexical scope (as opposed to locals). Per-threadness is a different dimension.

No ThreadLocalGlobal then? :) How about PerThreadGlobal?

@winksaville, I suppose you mean a module instance? If I understand your question correctly, then no, threads are orthogonal to module boundaries.

@chicoxyzzy, `global` as the standard name for the global object has been ruled out by TC39, because it would conflict with existing code. Either way, I don't think there would...

Still not a big fan of this feature, since conditional initialisation seems too ad-hoc and doesn't give you anything you cannot already express with suitable modularization. In my mind the...

@lars-t-hansen, yes, at least in the case of memories (not sure if that accurately describes table segments, though). Repurposing the current zero byte as a flag distinguishing passive from active...

@lukewagner, by bytecode, do you mean the binary? Nothing prevents you from defining a module that explicitly calls the start function again later, so I'm not sure such a restriction...

@lukewagner, I see. Are you talking about a runtime error, then? For example. the init instructions would trap if executed later? How difficult would it be for an implementation to...