rust/src/tools/rust-analyzer/crates/load-cargo, branch try-perfhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try-perf2025-07-31T08:55:10+00:00`cargo clippy --fix`2025-07-31T08:55:10+00:00Lukas Wirthme@lukaswirth.dev2025-07-31T08:30:22+00:00urn:sha1:a7b01aa04867ba0ee10f767f3819d47c45d9cc30Abtract away json protocol for proc-macro-srv2025-07-30T13:52:10+00:00Lukas Wirthme@lukaswirth.dev2025-07-30T13:31:18+00:00urn:sha1:2918a2b5505299e0d4164a776c0bdc745bb69736Add `fn load_workspace_into_db` variant for `ra_ap_load_cargo`'s `fn load_workspace`2025-07-03T21:09:49+00:00Vincent Escheregexident@gmail.com2025-07-02T08:32:46+00:00urn:sha1:7a67f31c39adda2eed7e71c1fe7dc7e1723e8242fix: Do not warn about proc-macro srv when sysroot is missing2025-07-03T09:51:31+00:00Lukas Wirthme@lukaswirth.dev2025-07-03T09:51:31+00:00urn:sha1:7e65c228f3e82293e3ecb1b2fc8b413d5e2ec7adRestructure proc-macro loading erros, differentiate hard error property on kind2025-07-03T07:28:53+00:00Lukas Wirthme@lukaswirth.dev2025-07-03T07:28:53+00:00urn:sha1:adcb38cb18a9d7b1cd09981e44316a5512dbc8d0feat: Show what cargo metadata is doing in status2025-06-16T16:05:44+00:00Lukas Wirthme@lukaswirth.dev2025-06-16T16:05:44+00:00urn:sha1:13f5866e96eb0347c278b40fa73a926dfe1546d3Fix comparison of proc macros2025-06-12T10:31:55+00:00Chayim Refael Friedmanchayimfr@gmail.com2025-06-12T10:22:44+00:00urn:sha1:6a0f4e59a898f07045e4b05d3ed66f3179100971
Comparing the TypeId is not enough, they also contain data.
refactor: Remove unnecessary `AsAny` trait2025-05-05T14:42:17+00:00Lukas Wirthlukastw97@gmail.com2025-05-05T14:04:57+00:00urn:sha1:941e8f1b155869d4ac3ae7392fc732bb1ebaac45remove a couple of clones2025-05-01T09:41:42+00:00Matthias Krügermatthias.krueger@famsik.de2025-05-01T09:41:42+00:00urn:sha1:3e196c00c2374263d943b5e2226164d4c5f122dballow using `null` to unset an environment variable2025-04-19T16:15:22+00:00jyngithub@jyn.dev2025-04-19T15:42:38+00:00urn:sha1:fdcc2faaa206f2fcecd5a1ee40e1db6a116c9500
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.