jyn 3b964a7105 allow using null to unset an environment variable ... this makes three changes: - all callsites of `toolchain::command` are changed to use `command(path, extra_env)`, instead of manually adding the env after the fact. - all `map<str, str>` are changed to `map<str, option<str>>`. - `command` checks for None and calls `env_remove` if so. this caught several places where environment variables weren't being propagated: - when running `rustc --print=target-libdir` - when running `cargo rustc -- --print=target-spec-json` - when running the custom DiscoverLinkedProjects config. I *think* this is for use with non-cargo build systems, so I didn't change it.		2025-04-19 12:15:22 -04:00
..
src	allow using null to unset an environment variable	2025-04-19 12:15:22 -04:00
Cargo.toml	enable doctest	2025-02-27 14:58:46 +01:00