Proposal: rename `wasi` target OS to `wasip1`

[ianprime0509]

Since WASI preview 2 has been officially launched, and implementations of it are available, the term "WASI" by itself has become ambiguous. Eventually, in the future, when WASI is stabilized, the unqualified term "WASI" should refer to the stabilized version.

The name "wasip1" for preview 1 (which is what Zig currently supports) seems to be the preferred name going forward in the WASI ecosystem, see for example WebAssembly/wasi-libc#478

This proposal doesn't cover how Zig might eventually support preview 2 (which would likely involve several other factors, such as wasi-libc support and integration with the component model on which preview 2 is based). It just proposes renaming the existing wasi target OS to eliminate ambiguity and pave the way for future developments in this area.

[jacobly0]

Does #19654 fit your needs?

[ianprime0509]

Thanks! That seems reasonable to me. One nit, though, is that I think it would make more sense to have WASI preview 1 be version 0.1.0 in that scheme, as preview 2 is labeled as 0.2.0 in the WIT IDL definitions. (Also, my understanding of the target query parsing code suggests to me that OS versions containing -, such as wasi.0.0.0-preview.1, would not be parseable, as the arch-OS-ABI triple is split on -, but I could be missing something)

[jacobly0]

(Also, my understanding of the target query parsing code suggests to me that OS versions containing -, such as wasi.0.0.0-preview.1, would not be parseable, as the arch-OS-ABI triple is split on -, but I could be missing something)

Yeah I was wondering the same thing, but your suggested versioning solves that neatly.

[andrewrk]

Solved in a2b834e.

-target wasm32-wasi.0.1.0 vs -target wasm32-wasi.0.2.0