-
Notifications
You must be signed in to change notification settings - Fork 439
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
Missing ability to access built older versions of the WebAssembly specification in archivable form #1736
Comments
Going forward, all new versions will be available at https://www.w3.org/standards/history/wasm-core-2/ |
I agree they should be made available here (especially since the w3c site will probably only have the inferior single-page HTML version). We have talked about this in the past, but never took action. FWIW, you should be able to at least build the old releases of the spec by checking out this repo at specific release tags, e.g., |
There does not appear to be a simple way to access built older versions of the WebAssembly specification, particularly 1.0, in archivable form (the various builds, i.e. PDF etc.)
I was at least able to find the W3C version of the core specification ( https://www.w3.org/TR/wasm-core-1/# ), but that appears to be all, and it doesn't appear to have any standardized archival download readily available.
Why care about 1.0?
There are two main use-cases I can think of for the WebAssembly 1.0 specification:
v128
), the support for these in browsers that are actually available on end-user devices will vary. There will be, for quite some time, the need to maintain WebAssembly 1.0-compliant versions of ecosystem software.It is thus important to keep available the specification versions that actually apply to these targets.
Workaround
A present workaround is to use the mirrors generated by WebAssembly project proposals that were forked from late-stage 1.0, i.e. https://webassembly.github.io/multi-value/core/_download/WebAssembly.pdf -- however, there are still some differences, so this is probably not a definitive 1.0.
The text was updated successfully, but these errors were encountered: