CR Request for WebAssembly Core - wasm-core #651
Labels
Awaiting Working Group
This includes editors and team contacts
Entering CR
First Candidate Recommendation
wg:wasm
Document title, URLs, estimated publication date
WebAssembly Core Specification, https://www.w3.org/TR/wasm-core-2/
Estimated publication date: ASAP
Abstract
This document describes release 2.0 of the core WebAssembly standard, a safe, portable, low-level code format designed for efficient execution and compact representation.
This is part of a collection of related documents: the Core WebAssembly Specification, the WebAssembly JS Interface, and the WebAssembly Web API.
Status
WD: existing status can be seen in the doc at the link above
Status for all the various states (including what the CR status will be) can be found in our Bikeshed boilerplate
files: https://github.com/speced/bikeshed-boilerplate/tree/main/boilerplate/wasm
Link to group's decision to request transition
https://github.com/WebAssembly/meetings/blob/main/main/2024/WG-06-12.md
Changes
Changes since 1.0 listed at https://www.w3.org/TR/wasm-core-2/#change-history
The following extension proposals have advanced from the CG:
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.
Requirements satisfied
Dependencies met (or not)
Dependencies are unlikely to change.
Wide Review
[TODO: horizontal review?]
Issues are tracked at https://github.com/WebAssembly/spec/issues
Email announcement at https://lists.w3.org/Archives/Public/public-webassembly/2024Jul/0000.html
Issues addressed
Issues are tracked at https://github.com/WebAssembly/spec/issues
Formal Objections
None raised
Implementation
All of these features have been implemented in all 3 major browser engines. A full feature matrix including version
information can be found at https://webassembly.org/features/
Patent disclosures
[TODO: link to IPP]
The text was updated successfully, but these errors were encountered: