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

Seek wide review for CR transition of wasm 2.0 #1804

Open
15 tasks done
dschuff opened this issue Sep 18, 2024 · 4 comments
Open
15 tasks done

Seek wide review for CR transition of wasm 2.0 #1804

dschuff opened this issue Sep 18, 2024 · 4 comments

Comments

@dschuff
Copy link
Member

dschuff commented Sep 18, 2024

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).

@dschuff
Copy link
Member Author

dschuff commented Sep 18, 2024

Results of accessibility questionnaire moved to
#1805

@dschuff dschuff added a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. and removed a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. labels Sep 18, 2024
@aphillips
Copy link

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
Copy link
Member Author

dschuff commented Sep 18, 2024

Thanks, I'll push it back.

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants