chore: update to WASI 0.2.2 #28
Open
Conversation
This file contains 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
Signed-off-by: Roman Volosatovs <[email protected]>
rvolosatovs
force-pushed
the
feat/wasi-0.2.2
branch
from
defbbf3
to
b6d1f92
Compare
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.
Note, that the interface version in the WIT is purposefully not changed - doing so (e.g. using
0.2.0-draft.1) means that hosts that would want to support both versions would now need to duplicate all binding implementations and deal with duplicate I/O package dependencies.There's no reason for this complexity, however, because the host may choose any version of I/O package for implementation, e.g. component interface version depending on
wasi:io/[email protected]can successfully import host interface version depending onwasi:io/[email protected](see an example of this working in wasmCloud/wasmCloud#3312 if interested)