-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Note the state of the proposal #50
Conversation
The CG has reached agreement that the future of threads in WebAssembly goes through the shared-everything-threads proposal. This change tries to communicate the "legacy" nature of wasi-threads: still valuable in some cases but planned for eventual deprecation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@@ -3,6 +3,16 @@ | |||
A proposed [WebAssembly System Interface](https://github.com/WebAssembly/WASI) | |||
API to add native thread support. | |||
|
|||
> __NOTE__: this proposal is considered a legacy proposal, retained for engines |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we perhaps mention there are runtimes already implementing this proposal (WAMR specifically) and teams that rely on it, so it will be around for quite some time?
I understand we want to encourage people to wait and use the new proposal, but if there are people like us who got stuck with this proposal and can't migrate, they can open a ticket in this repo to contact us for any relevant topic - I'll be actively monitor this repo and reply to those tickets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, those are good points. I'll try to add something about that. Can you think of anyone else I should put on the "contact these people" list?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please feel free to include me.
however, i'm not sure if such a list is necessary.
a list of links to github issues of relevant repos, including this repo, should be enough.
it probably even works better than a person-level contact list.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please feel free to include me too if the list is added.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
As suggested by @yamt in a [comment], it may be better to avoid highlighting WAMR exclusively in the top-level "warning." Instead, this updates the implementation status for known engines. [comment]: WebAssembly#50 (comment)
As suggested by @yamt in a [comment], it may be better to avoid highlighting WAMR exclusively in the top-level "warning." Instead, this updates the implementation status for known engines. [comment]: #50 (comment)
The CG has reached agreement that the future of threads in WebAssembly goes through the shared-everything-threads proposal. This change tries to communicate the "legacy" nature of wasi-threads: still valuable in some cases but planned for eventual deprecation.