Add support for WebAssembly forks to find-specs #529
Comments
tidoust
added a commit
that referenced
this issue
Jan 31, 2024
This updates the find-specs script to also look for new WASM proposals in: https://github.com/WebAssembly/proposals/blob/main/README.md Only phase 3+ proposals are being considered, in accordance with: #1181 (comment) ... which itself derives from: web-platform-tests/interop#589 (comment) The script now filters out specs that cannot be fetched (some WASM proposals at phase 3+ do not have a proper spec). Fix #529.
tidoust
added a commit
that referenced
this issue
Feb 1, 2024
This updates the find-specs script to also look for new WASM proposals in: https://github.com/WebAssembly/proposals/blob/main/README.md Only phase 3+ proposals are being considered, in accordance with: #1181 (comment) ... which itself derives from: web-platform-tests/interop#589 (comment) The script now filters out specs that cannot be fetched (some WASM proposals at phase 3+ do not have a proper spec). Fix #529.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a number of repos under https://github.com/WebAssembly/ that are forks (in #528 sense) of the main specs; we should determine which one should be considered for browser-specs, and possibly add them all to web-specs. In general, we should make it so that find-specs reports about them.
The text was updated successfully, but these errors were encountered: