Seek wide review for CR transition of wasm 2.0

[dschuff]

This is a meta issue to track wide review steps for the specification.
See How to do wide review for details.

This is a request for transition for all 3 WebAssembly specifications, namely the core spec, which defines the core code format and semantics;
the JS API specification, which provides a JavaScript API for interacting with WebAssembly; and the Web API specification, which describes the integration of WebAssembly with the broader web platform.

All of the analysis herein concerns the changes made since Wasm 1.0. These are listed
here and include the following extension
proposals:
Sign extension instructions; Non-trapping float-to-int conversions; multi-value block types and function results;
reference types, table instructions, and multiple tables; bulk memory and table instructions; SIMD vector instructions. Links to overviews of each proposal can be found in the proposal's respective github repo (these are listed here).

• the groups listed in the WG's charter, especially those who manage dependencies
• the groups jointly responsible for a particular document (N/A).
• the horizontal groups:
  • Accessibility
    • Work through this questionnaire - local issue
    • request a review via GitHub from APA (issue)
  • Architecture
    • Ask the TAG for review; see how to work with the TAG
    • If you are developing javascript APIs you may also want to ask [email protected], a technical discussion list shared by W3C and ECMA's TC 39
  • Internationalization
    • Read the Request a review page
    • work through the Short Checklist - local issue
    • request a review via GitHub - issue
  • Privacy
    • Write a "Privacy Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy, Mitigating Browser Fingerprinting in Web Specifications, and RFC6973
    • request a review via GitHub from the Privacy Interest Group
  • Security
    • Write a "Security Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy
    • request a review via GitHub
• Other outreach (if applicable)

[dschuff]

Results of accessibility questionnaire moved to
#1805

[aphillips]

The request for I18N review of exactly two weeks which coincides with TPAC is not going to succeed on the requested schedule. Our first WG teleconference after TPAC is 2024-10-03 and that is the earliest date our review might be completed.

[dschuff]

Thanks, I'll push it back.

[dschuff]

For review convenience, here is a list of the explainers for the proposals that have gone into 2.0, compared to 1.0 (currently in REC state). These are informal descriptions of the proposed changes and are not canonical, but describe an overview of the feature and could be useful in determining whether there is anything of interest for horizontal reviewers.

Note again also that the core spec contains a list of additions since version 1.0 and summarizes the addition to the core spec. The table summarizes the effect on the JS spec. The Web spec is unchanged since 1.0

Explainer	Specs affected	JS Spec difference summary
Nontrapping float-int conversion	Core
Sign-extension operators	Core
Multi-value block and function returns	Core, JS	Multi-value returns can be passed into JS as JS Arrays
JS BigInt Integration	JS	Wasm i64 values can be passed to and from JS as BigInt values
Reference Types	Core, JS	References to JS objects can be passed to and from Wasm as externref values.
Bulk Memory and table instructions	Core
SIMD Vector instructions	Core