-
Notifications
You must be signed in to change notification settings - Fork 298
1.81.0 release announcement #1386
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
Conversation
I saw there is a section in this announcement about the WASI 0.1 target being renamed. In this same release the WASI 0.2 target has also been upgraded from Tier 2 to Tier 3. I just filed a PR for a post explaining what that means in: #1391. If folks are okay with publishing the WASI 0.2 post on the same day; Maybe we could include a small section at the bottom mentioning that ### WASI 0.2 target has reached tier 2
The `wasm32-wasip2` target is now supported as a tier 2 target. This means it is
guaranteed to build, can now be installed via `rustup`. To
conditionally target WASI 0.2, the following `cfg` attribute can be used:
```rust
#[cfg(all(target_os = "wasi", target_env = "p2"))]
mod wasip2 {
// items go here
}
```
For more details see the
[WASI 0.2 tier 2 announcement post](https://blog.rust-lang.org/2024/09/05/wasip2-tier-2.html). |
d646270
to
fcd066b
Compare
fcd066b
to
c74dea5
Compare
cc @rust-lang/release