JF Bastien

We should replace it instead, with forwarding links, and host the editor's draft on webassembly.org. This probably fits in [the webassembly.org maintenance discussion](https://docs.google.com/document/d/1pTG4BtIETf1wkZ5Xq3OHAKadv-hi13p7_CGHfBon9Yw/edit).

Dup #913 and #949?

FWIW we test this behavior here: https://trac.webkit.org/browser/webkit/trunk/JSTests/wasm/function-tests/i64-from-js-exceptions.js

EDIT: Moved to #91.

EDIT: Moved to #91.

I'd like this bug to focus solely on the memory model. My intent is to list what's different from other work, and get the memory model work started. I'm happy...

> I only have the lightest of opinions on this matter at the moment, but others have raised the issue that an operational model may be a better fit than...

This is for the JS API. It should not be optional for that API. If we do offsets, we should use the same offset (file or function) as for the...

I like Andreas's proposal.

@bnjbvr would you be willing to tackle this and provide a PR? @rossberg-chromium 's proposal seems acceptable to all.