Note that Rust stable supports WASI as of 1.35

[callahad]

Unless there's a compelling reason to force people into nightly builds, we should probably call attention to WASI support in stable Rust.

[tschneidereit]

Ooh, good call—thank you!

[callahad]

Spotted similar references in a few other CraneStation/ repos. I'll get those updated in just a sec :)

[sunfishcode]

I would prefer not to drag people through the triple changing again or explain the target macros changing and they have to write #[cfg(any(target_env = "wasi", target_os = "wasi"))] if they don't want their code to break in a future Rust release. Also, rust-lang/rust#59727 is important. In all, my recommendation would be to leave the instructions pointed at nightly Rust for now.

[tschneidereit]

That's a good point. In particular the target triple. However, ideally we'd support the -unknown part as optional. It's my understanding that that's how target triples are meant to be interpreted to begin with?

[callahad]

@sunfishcode All three of those pull requests are currently in the Rust beta branch... would it be fair to point people to that (and thus to Stable, once 1.36 gets released), or are you still concerned about other outstanding issues that need to shake out?

[sunfishcode]

Triples in general have flexibility here, but the Rust targeting system requires an exact match, so the -unknown isn't optional in rustc. It's currently required on stable and not accepted on beta.

The PRs I linked to are the important ones, so if those are on beta, then that sounds fine.

Of course, WASI itself is still wasi_unstable. It's relatively stable at this point, but it's important people know that this is just the beginning :-).