Add the WebAssembly JS and Web APIs #43
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in today's WinterCG meeting, although the WebAssembly JS API (as well as the web API) is built into all mainstream JS engines, it is not officially part of the JS language. (In fact, Ladybird, the Serenity OS browser, implements the JS and wasm engines separately.)
As such, since web-interoperable runtimes are expected to support WebAssembly, it follows that the WebAssembly JS and Web API should be included in the list.
(The WebAssembly Web API should be included as well, but cannot be included at the moment because fetch'sResponse
class is a precondition for it. See #27.)