Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebAssembly 2024-09-17 > 2024-10-01 #91

Closed
dschuff opened this issue Sep 18, 2024 · 2 comments
Closed

WebAssembly 2024-09-17 > 2024-10-01 #91

dschuff opened this issue Sep 18, 2024 · 2 comments
Labels
LC Working Draft approaching Candidate Recommendation pending This issue needs to get a reviewer assigned to it REVIEW REQUESTED

Comments

@dschuff
Copy link
Member

dschuff commented Sep 18, 2024

This is a request for transition for version 2.0 of 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.

  • What and when is your next expected transition?
    CR, as soon as horizontal review is done.

  • What has changed since any previous review?
    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).

  • Please point to the results of your own self-review (see https://w3c.github.io/apa/fast/checklist.html)
    Check against a11y checklist for CR transition WebAssembly/spec#1805

  • Where and how to file issues arising?
    https://github.com/WebAssembly/spec/issues

  • Pointer to any explainer for the spec?
    There is not an explainer for the entire spec (and in any case it is fairly large). Links to explainers/overviews for each
    of the 5 proposals can be found in the proposal's respective github repo (these are listed here).

Other comments:
Since WebAssembly is a specification for the representation and semantics of computation, it seems there is very little interaction with accessibility principles.

@dschuff dschuff added LC Working Draft approaching Candidate Recommendation pending This issue needs to get a reviewer assigned to it REVIEW REQUESTED labels Sep 18, 2024
@dschuff
Copy link
Member Author

dschuff commented Sep 18, 2024

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

@ruoxiran
Copy link

ruoxiran commented Oct 9, 2024

no comments or requests from APA, thank you.

@ruoxiran ruoxiran closed this as completed Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LC Working Draft approaching Candidate Recommendation pending This issue needs to get a reviewer assigned to it REVIEW REQUESTED
Projects
None yet
Development

No branches or pull requests

2 participants