Ben Smith

Sorry, I'm a bit confused. I see that we would want to be able to dynamically link the stack pointer, but don't we need mutable imported/exported globals for that? And...

OK, but don't you need this for load-time dynamic linking w/out threads? I'm just wondering if this is a separable proposal, or if it only is needed w/ the threading...

OK, now I see. Since memory is now shared, you need some mechanism for thread-local values. We could do this using mutable globals, but we could also do it using...

@dtig right, the change here would make the following a malformed module instead of an invalid module: `(i32x4.extract_lane 5)` or the equivalent binary `\xfd\x1b\x05`. AFAIK, VMs don't often make a...

OK, the GC issue makes sense to me. This PR came out of [this discussion](https://github.com/WebAssembly/threads/pull/116#discussion_r251070565). I assumed that we would create a new Memory object (as Lars describes above), so...

> Do you know where I can propose meta-stuff like requirement of a design rationale doc for all Wasm proposals? @Robbepop I'd suggest bringing this to the CG meeting for...

> I can't see anything explicit, but is the memarg part of the existing atomics' binary encoding intended to be used this way in the future? Yes, I assumed we...

@conrad-watt that looks right to me, though I think we'd just inline the `memargf` (as with `call_indirect` [in this definition](https://webassembly.github.io/spec/core/binary/instructions.html#binary-instr)). As for the opcode to choose, I don't have a...

Yeah, I was generally providing the minimal API that would support the desired functionality. But you're right, providing the type and mutability seem useful. Agreed with @rossberg that reflecting types...

Oops, maybe better to put my comment from #11 here: There wasn't a poll about this in the CG meeting, but there seemed to be interest in exploring adding a...