You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: