Blog post: Changes to Rust's WASI targets #1302
Conversation
Co-authored-by: Christopher Serr <christopher.serr@gmail.com>
|
Talked to @alexcrichton over Zulip today, and he said it looks good. I shared an earlier draft with him last week, and the version I posted here already incorporated all of his feedback. He's currently traveling though, and can't directly approve it until he's back - hence this update. |
There was a problem hiding this comment.
I think we're burying the lead a bit here. This sentence might make readers wonder about why this post is on the main Rust blog instead of Inside Rust or even somewhere else. They may ask themselves "why should I read a post about a target I shouldn't use yet?".
The main story here is that there is a shift in target naming coming that will require user action, and we want to inform people as early as possible. I think that should be at the very top of the post. Let's make sure everyone knows as quickly as possible about what information they'll get from this post.
Co-Authored-By: Wesley Wiser <wwiser@gmail.com>
Co-Authored-By: Ryan Levick <ryan.levick@fermyon.com>
yoshuawuyts
force-pushed
the
updates-to-rusts-wasi-targets
branch
from
43105eb
to
f2baed3
Compare
|
@rylev Those are great points, thank you. Is this better? |
|
Reviews went through a lot quicker than expected - I think we're good to publish this today. Thanks everyone! |
This explains the upcoming changes to Rust's WASI targets, starting in Rust 1.78. This supersedes #1099. I put the post date in for 2024-04-10 (two days from now). Thanks!
cc/ @alexcrichton, @wesleywiser