Andrew Scheidecker

> First, wasm memories cannot be shrunk, so once an index is in-bounds, it is in-bounds for as long as the instance lives. Yes, the API doesn't support shared memories,...

> A more efficient and direct call interface (in both directions) is something we have discussed. It clearly is desirable, but it is less clear how to provide it or...

If `wasm_val_t` contains an indirect pointer to `wasm_v128_t`, it would be essential that the caller is able to allocate the `wasm_v128_t` on the stack, and that ownership of that memory...

> Yeah, I understand the suggestion, but I'm sorry to say that my prior exposure has elicited an allergy to clang-format. Symptoms are cringing pain and curling toe nails when...

> Could you upload a PR with the changes that result for formatting with BasedOnStyle: Chromium so we can see how intrusive it would be? @sbc100 See #115.

Yes, it's possible, but not without changes to this API. WAVM supports this by splitting the WASM store into "compartments" and "contexts". Contexts correspond to thread-local state, and compartments to...

> I can imagine engines supporting both interfaces natively. That's what I'd like to avoid. > I'd also be totally fine with adding an adapter for the other direction, as...