rami3l

> I see where you're going and it makes some sense, but at the same time as a user I would be a little annoyed if rustup sprayed a bunch...

> write all the env files to a rustup subdirectory @ChrisDenton @djc To clarify, what I meant is that we already have `$CARGO_HOME` to populate our `env.*` files to, my...

> That doesn't answer this question: > > > Why do you want this? What problem are you trying to solve? @djc @chrisdenton There are people who would like to...

> This issue is not a dupe of [#4099](https://github.com/rust-lang/rustup/issues/4099) Any other target has the same issue, i just happened to use wasm32-wasi as mentioned in the problem description > >...

@vorporeal Hi, thanks for filling this issue! AFAIK the target list is designed mostly for embedded projects that essentially require extra targets to be installed, and it should be considered...

100% agree; we need to discuss with upstream first to confirm what needs to be done on our side.

@vi Thanks for filing this issue! I think it's a bit dangerous to hardcode anything from our side, but given the repeated requests (which led to patches like #3453 and...

@ngoldbaum It should be noted though, if I were to directly add this note in Rustup today, it will not be delivered to the users in time, since we expect...

@InfyniteHeap FYI https://github.com/microsoft/windows-rs/issues/3119 has been closed, so you might restart your work on this one!

@InfyniteHeap According to https://github.com/microsoft/windows-rs/issues/3148#issuecomment-2263527164, you may now test how the upstream change works with this PR via `Cargo.toml`'s [`[patch]` section](https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section).