[w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)

こんにちは TAG-さん!

I'm requesting a TAG review of {{feature}}.

This is a request for transition for version 2.0 of 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-js-api-2/) specification, which provides a JavaScript API for interacting with WebAssembly; and the [Web API](https://www.w3.org/TR/wasm-web-api-2/) specification, which describes the integration of WebAssembly with the broader web platform.

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 also that the specifications contain change history sections summarizing additions to each spec ([core](https://www.w3.org/TR/wasm-core-2/#release-20), [JS](https://www.w3.org/TR/wasm-js-api-2/#release-20), [Web](https://www.w3.org/TR/wasm-web-api-2/#release-20))
listing and summarizing additions since version 1.0. The table summarizes the effect on the JS spec. The Web spec is unchanged since 1.0

| Explainer  | Specs affected 
|----|---|
| [Nontrapping float-int conversion](https://github.com/WebAssembly/nontrapping-float-to-int-conversions/blob/main/proposals/nontrapping-float-to-int-conversion/Overview.md) | Core
| [Sign-extension operators](https://github.com/WebAssembly/sign-extension-ops/blob/master/proposals/sign-extension-ops/Overview.md) | Core
| [Multi-value block and function returns](https://github.com/WebAssembly/multi-value/blob/master/proposals/multi-value/Overview.md) | Core, JS 
| [JS BigInt Integration](https://github.com/WebAssembly/JS-BigInt-integration?tab=readme-ov-file) | JS 
| [Reference Types](https://github.com/WebAssembly/reference-types/blob/master/proposals/reference-types/Overview.md) | Core, JS 
| [Bulk Memory and table instructions](https://github.com/WebAssembly/bulk-memory-operations/blob/master/proposals/bulk-memory-operations/Overview.md) | Core
| [SIMD Vector instructions](https://github.com/WebAssembly/simd/blob/main/proposals/simd/SIMD.md) | Core

  - WPT Tests: The Core tests live in the spec repo (with a mirror [here](https://github.com/WebAssembly/testsuite)). The JS API tests are canonically [here](https://github.com/WebAssembly/spec/tree/main/test/js-api) but are mirrored to WPT.
  - User research: N/A, but our process does require implementation feedback from toolchain authors (as Wasm code is generated by toolchains)
  - Security and Privacy self-review²: https://github.com/WebAssembly/spec/issues/1830
  - GitHub repo: https://github.com/WebAssembly/spec
  - Primary contacts:
      - Derek Schuff (@dschuff), Google, WG/CG co-chair
      - Andreas Rossberg (@rossberg), Independent, spec editor
      - Luke Wagner (@lukewagner), Fastly, WG co-chair
      - Thomas Lively (@tlively), Google, CG co-chair
      - Conrad Watt (@conrad-watt), NTU, CG co-chair
  - Organization/project driving the specification: Spec graduates from WebAssembly CG to WG according to our [process](https://github.com/WebAssembly/meetings/blob/main/process/phases.md)
  - Multi-stakeholder support³:
    - All 4 major browsers have shipped all of the proposals in WebAssembly 2.0 (versions listed [here](https://webassembly.org/features/) ... I can give more details if you want)

Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: No deadline, but please review ASAP, as we have another batch of features to merge into the spec, and we hope to be more timely about that than we were about this one.
  - The group where the work on this specification is currently being done: WebAssembly CG and WG
  - The group where standardization of this work is intended to be done (if different from the current group): WebAssembly WG
  - Major unresolved issues with or opposition to this specification: None
  - This work is being funded by: Many organizations. 


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1002
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1002@github.com>