Tracking issue for improvements to Rust itself

[retep998]

This issue will track every issue and PR related to improving Rust itself on Windows. Please keep discussion of specific issues to separate issues. Comments here should only be to suggest changes to this list.

Not started

• Pure Rust Windows target with no external C toolchain dependency, taking advantage of LLD and raw-dylib.
• Add debug CRT option. Has some old stagnant PRs that can be revived to easily get this going.
• Do something to finally stabilize the functionality of kind="static-nobundle" in some form.
• Some way to do Structured Exception Handling directly in Rust.
• Spawning processes needs a lot of work on Windows
  • Inheriting handles is terrible and should be changed
  • When PATH is modified Command does its own logic to locate the exe to match unix behavior and it is different from what Windows does.
  • Provide way to override the entire command line string on Windows.
• Let build scripts specify custom linker arguments.
• Native support for resource files and manifests in Rust.
• Ability to link to object files directly.
• Fix env_clear on Windows.

Proposal in progress

• A way to specify which version of Windows your program requires and generating optimal code based on that. Pre-RFC on Zulip

Implementation in progress

• #[link(kind="raw-dylib")]

Completed

[Lokathor]

• Tracking issue for RFC 2627: #[link(kind="raw-dylib")]

[crlf0710]

• The mountain of Rust, Windows, and MSVC

[matklad]

• std::fs::revome_dir_all() doesn't work on windows

[nico-abram]

@retep998 env_clear seems to be fixed: rust-lang/rust#31259

Just wanted to mention it in case you wanted to update the checkbox in your comment

[tbu-]

@retep998 #[link(kind = "raw-dylib")] has also stabilized for a long time already.