Repository navigation
Add support for pure WASIp2 builds - #44
Merged
Merged
Conversation
This changes the `wasm32-wasip2` build target to really target WASIp2, without any P3 APIs or Component Model async features. In most regards, the behavior is the same, but there are some key differences in custom WIT bindings. Specifically, where WASIp3 `streams`s and `future`s are mapped to JavaScript `ReadableStream`s and `Promise`s, WASIp2 bindings expose `wasi:io` interfaces directly. For builtin features, the key difference is that the inbound HTTP handler can't process multiple requests concurrently, since the incoming handler only returns once the request has been fully handled.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This changes the
wasm32-wasip2build target to really target WASIp2, without any P3 APIs or Component Model async features.In most regards, the behavior is the same, but there are some key differences in custom WIT bindings. Specifically, where WASIp3
streamss andfutures are mapped to JavaScriptReadableStreams andPromises, WASIp2 bindings exposewasi:iointerfaces directly. For builtin features, the key difference is that the inbound HTTP handler can't process multiple requests concurrently, since the incoming handler only returns once the request has been fully handled.