doc: update Wasm threads support status#5739
Merged
abrown merged 1 commit intobytecodealliance:mainfrom Feb 7, 2023
Merged
Conversation
Member
Author
|
(Also, I propose we add a new, separate documentation page to explain the WASI proposals and their level of support--thoughts?) |
Member
Author
|
cc: @tschneidereit |
Member
Author
|
Related PR for the roadmap documentation: WebAssembly/website#313 |
alexcrichton
approved these changes
Feb 7, 2023
Member
alexcrichton
left a comment
There was a problem hiding this comment.
Having a separate section for WASI proposals makes sense to me yeah
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.
As requested here, this updates the documentation to indicate that the WebAssembly threads proposal is now supported. It looks like the spec tests are already running in
build.rsbut if there is any issue with that it can be resolved separately; this change simply documents the current level support on this page.