Ben Visness

Sub-proposal: `virtual` mode

4

This issue tracks discussion of the **`virtual` mode** sub-proposal. This proposal is one possible component of the eventual Memory Control MVP. Please make sure to read the [full sub-proposal document](https://github.com/WebAssembly/memory-control/blob/main/proposals/memory-control/virtual.md).

This issue tracks discussion of the **`maplength`** sub-proposal. This proposal is one possible component of the eventual Memory Control MVP. Please make sure to read the [full sub-proposal document](https://github.com/WebAssembly/memory-control/blob/main/proposals/memory-control/maplength.md).

This issue tracks discussion of the **static memory protection** sub-proposal. This proposal is one possible component of the eventual Memory Control MVP. Please make sure to read the [full sub-proposal...

This issue tracks discussion of the **BYOB for WebAssembly.Memory** sub-proposal. This proposal is one possible component of the eventual Memory Control MVP. Please make sure to read the [full sub-proposal...

Placeholder issue to address the question of stream APIs on the web, and how they would integrate with this proposal. (See https://github.com/WebAssembly/memory-control/pull/12#discussion_r1621301910.) @dtig, feel free to edit this comment into...

Adds explicit steps to run memtype and tabletype validation and throw a RangeError on failure. This explicitly satisfies the preconditions from the wasm embedding spec, and removes the need for...

[js-api] Memory and table allocation pre-conditions not validated

3

The [mem_alloc](https://webassembly.github.io/spec/core/appendix/embedding.html#mathrm-mem-alloc-xref-exec-runtime-syntax-store-mathit-store-xref-syntax-types-syntax-memtype-mathit-memtype-xref-exec-runtime-syntax-store-mathit-store-xref-exec-runtime-syntax-memaddr-mathit-memaddr) and [table_alloc](https://webassembly.github.io/spec/core/appendix/embedding.html#mathrm-table-alloc-xref-exec-runtime-syntax-store-mathit-store-xref-syntax-types-syntax-tabletype-mathit-tabletype-xref-exec-runtime-syntax-ref-mathit-ref-xref-exec-runtime-syntax-store-mathit-store-xref-exec-runtime-syntax-tableaddr-mathit-tableaddr) operations in the wasm embedding spec have pre-conditions asserting that the memory and table types are valid. The JS API spec does not actually ensure that...

(Bikeshed) Should we rename the parameters for `Table.get` and `Table.set`?

1

@backes points out in [this comment](https://github.com/WebAssembly/memory64/pull/90#discussion_r1810867815) that perhaps we should rename the `index` parameter on `Table.get` and `Table.set` to `address` as a result of #67. I'm not sure we want...

Resolves #1909.

Unclear meaning of "is exnref" in JS API

2

ToJSValue asserts that the input type is neither v128 nor `ref.exn exnaddr`. To enforce this, there are several places in the spec that say something like "If resultType is v128...