Daniel Ehrenberg

Being independent of various things sounds like a great goal for keeping these specs clear, meaningful and capable of evolving into the future. If there's sufficient non-normative text that can...

Yeah, sounds like we should rewrite how that cache works (again). The relevant text is in the current JS API spec, not even this repository. I'll think about the phrasing.

@devsnek The purpose of this issue is to find general, cross-environment solutions to the problem you are articulating. One possibly would be a "host hook" to let, say, WASI do...

What are the differences intended between the WebAssembly and JavaScript memory models? From [these notes](https://github.com/WebAssembly/meetings/blob/master/2017/CG-05.md) I see discussion of tearing on non-aligned memory accesses. Is there a difference in what...

FWIW I wrote Lars's semantics up [as a BigInt pull request](https://github.com/tc39/proposal-bigint/pull/80). I think with some refactoring, we could make the ES spec easy to call into directly from Wasm, and...

@rossberg-chromium Do you think we should have two distinct memory models which refer to the same piece of underlying memory? How would users and implementers be able to reason about...

@jfbastien Sorry for getting off-topic, filed https://github.com/WebAssembly/threads/issues/68 for that discussion.

Yeah, I agree that I'd like to separate these more complex questions from this proposal (so I do somewhat agree with @devsnek 's :confused: reaction), but I find that many,...

Is the expectation then that no one is using global exports? Maybe they could just be omitted for now so that no one starts depending on them, until browsers are...

A flag in the wasm binary format?