spec
spec copied to clipboard
WebAssembly specification, reference interpreter, and test suite.
Answers to questions to consider from https://www.w3.org/TR/security-privacy-questionnaire/ (organized into paragraph form but with references to each question in parens). https://www.w3.org/TR/fingerprinting-guidance/ and https://www.rfc-editor.org/rfc/rfc6973.html have also been consulted but do not ask...
I don't have time to investigate this further currently (and my OCaml knowledge is limited), but after #1796 we now fail most tests in the memory64 and js-promise-integration repositories, which...
This is a meta issue to track wide review steps for the specification. See [How to do wide review](https://www.w3.org/Guide/documentreview/#who_to_ask_for_review) for details. This is a request for transition for all 3...
Results of accessibility [questionnaire](https://w3c.github.io/apa/fast/checklist.html): This is a request for transition for all 3 WebAssembly specifications, namely the [core](https://www.w3.org/TR/wasm-core-2/) spec, which defines the core code format and semantics; the [JS API](https://www.w3.org/TR/wasm-core-2/)...
Some latex tables in the core spec use the extra space argument to add extra vertical space between table rows, e.g. the `\\[1ex]` on line 660 of this example from...
As the title states, there is some markup in the TOC, like for example in Validation->Types->Function Types there is a single child node named "[t1n] [syntax/types:syntax-functype] [t2m]". This is sins...
The PR #1796 changed the reference interpreter to generate these new commands by default in `arrange.ml`. Unfortunately this breaks downstream clients that consume `.bin.wast`. Would it be possible to only...
certain wasm runtimes creatively misuse UINT32_MAX to represent alternatives, for example in exception handling implementations to differentiate `catch` from `catch_all`. it'd perhaps be a good idea to make sure such...