should memory be exported as well?

[yamt]

• there seems to be a consensus memory should be imported for wasi-threads. clarification: https://github.com/WebAssembly/wasi-threads/pull/20
• on the other hand, it's said that memory should be exported in wasi: https://github.com/WebAssembly/WASI/blob/main/legacy/application-abi.md#current-unstable-abi
• it's a bit redundant to both import and export a memory.
• a side note: released versions of LLVM wasm-ld doesn't seem to support both import and export memory. https://reviews.llvm.org/D135898

discussions: https://github.com/WebAssembly/wasi-libc/pull/369#discussion_r1053853546 https://github.com/WebAssembly/wasi-threads/pull/19#discussion_r1061484551 https://github.com/WebAssembly/WASI/pull/48#discussion_r289338186

[sbc100]

As a reference point, emscripten has been shipping multi-threaded apps based on workers (instance-per-thread) for a while now, and the shared memory is always imported by the module in this case (and never exported).

[abrown]

@sunfishcode and I had talked some time ago about switching the WASI paradigm from "export the memory" to "import the memory." It might break some things but I would recommend discussing that over in the WASI repository and seeing if that change can be made now before too many things depend on that fact.

[yamt]

@sunfishcode and I had talked some time ago about switching the WASI paradigm from "export the memory" to "import the memory." It might break some things but I would recommend discussing that over in the WASI repository and seeing if that change can be made now before too many things depend on that fact.

it makes sense. i created an issue there. https://github.com/WebAssembly/WASI/issues/502