Skip to content
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

disambiguate wasi by renaming it to wasip1 #1053

Closed
codefromthecrypt opened this issue Apr 27, 2023 · 0 comments · Fixed by #1055
Closed

disambiguate wasi by renaming it to wasip1 #1053

codefromthecrypt opened this issue Apr 27, 2023 · 0 comments · Fixed by #1055
Milestone

Comments

@codefromthecrypt
Copy link

Comments happened on #964 (comment) post merge, about how "wasi" is ambiguous, and Go disambiguated it with "wasip1". As the issue was already merged, comments didn't really lead to action.

Since then, rust and JS are beginning to enforce a wasi version similar, if not exactly the same as the Go discussion. I think we shouldn't really keep "wasi" knowing this, especially as the whole thing is new might as well do it right.

My suggestion is to keep the short name go uses "wasip1" as we know it is incompatible with subsequent versions. Without this, runtimes can't use the OS to figure out if the code might run or not, invalidating the concept entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants