about summary refs log tree commit diff
path: root/src/tools/rust-analyzer/crates/load-cargo
AgeCommit message (Collapse)AuthorLines
2025-07-31`cargo clippy --fix`Lukas Wirth-4/+4
2025-07-30Abtract away json protocol for proc-macro-srvLukas Wirth-1/+1
2025-07-03Add `fn load_workspace_into_db` variant for `ra_ap_load_cargo`'s `fn ↵Vincent Esche-8/+25
load_workspace`
2025-07-03fix: Do not warn about proc-macro srv when sysroot is missingLukas Wirth-14/+26
2025-07-03Restructure proc-macro loading erros, differentiate hard error property on kindLukas Wirth-22/+18
2025-06-16feat: Show what cargo metadata is doing in statusLukas Wirth-1/+1
2025-06-12Fix comparison of proc macrosChayim Refael Friedman-1/+5
Comparing the TypeId is not enough, they also contain data.
2025-05-05refactor: Remove unnecessary `AsAny` traitLukas Wirth-4/+0
2025-05-01remove a couple of clonesMatthias Krüger-1/+1
2025-04-19allow using `null` to unset an environment variablejyn-1/+1
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-04prefer default over newBenjaminBrienen-1/+1
2025-03-29fix: Fix, clarify and require a value for `proc_macro_cwd` of `CrateData`Lukas Wirth-1/+1
2025-03-23chore: Remove unused dependenciesLukas Wirth-1/+0
2025-03-15cargo fmtBenjaminBrienen-8/+9
2025-03-12Salsify the crate graphChayim Refael Friedman-19/+12
I.e. make it not one giant input but multiple, for incrementality and decreased memory usage for Salsa 3 reasons.
2025-03-10internal: port rust-analyzer to new SalsaDavid Barsky-1/+1
2025-03-07Log build script error output in `load_cargo::load_workspace_at`Arthur Baars-0/+8
2025-02-17Use correct working directory for non-workspace proc-macro executionMehul Arora-1/+0
2025-02-05Do not include excluded files even when the client opens themChayim Refael Friedman-1/+3
This require a pretty big modification, because this is a new kind of file: exists - but ignore it.
2025-01-24Explicitly add buildfiles when constructing ProjectFoldersDavid Richey-0/+18
2025-01-16Partially back out "fix: Fix sourceroot construction for virtual manifests"Lukas Wirth-4/+1
2025-01-02Store token trees in contiguous `Vec` instead of as a treeChayim Refael Friedman-5/+5
I expected this to be faster (due to less allocations and better cache locality), but benchmarked it is not (neither it is slower). Memory usage, however, drops by ~50mb (of `analysis-stats .`). I guess tt construction is just not hot. This also simplifies using even less memory for token trees by compressing equal span, which I plan to do right after. Some workflows are more easily expressed with a flat tt, while some are better expressed with a tree. With the right helpers, though (which was mostly a matter of trial and error), even the worst workflows become very easy indeed.
2024-12-30Move proc-macro protocol into legacy moduleLukas Wirth-1/+1
2024-12-30Decouple proc-macro server protocol from the server implementationLukas Wirth-6/+6
2024-12-18Remove salsa from proc-macro server dep treeLukas Wirth-1/+1
2024-12-12fix: Fix sourceroot construction for virtual manifestsLukas Wirth-41/+5
2024-12-09Fix config guard lock for ratoml testsLukas Wirth-2/+2
2024-12-07Watch for user config ratomlAli Bektas-2/+22
2024-09-30Gate `#[test]` expansion under `cfg(test)`.Chayim Refael Friedman-4/+1
This will mean users opting to not activate `cfg(test)` will lose IDE experience on them, which is quite unfortunate, but this is unavoidable if we want to avoid false positives on e.g. diagnostics. The real fix is to provide IDE experience even for cfg'ed out code, but this is out of scope for this PR.
2024-09-30Provide an config option to not set `cfg(test)`Chayim Refael Friedman-0/+3
2024-09-26Include buildfiles in vfsDavid Richey-0/+5
2024-09-11Properly set the working directory for proc-macro executionLukas Wirth-1/+10
2024-09-11Lift out workspace related data into a separate query to preserve crategraph ↵Lukas Wirth-6/+10
deduplication
2024-08-12Auto merge of #17864 - Veykril:lsif, r=Veykrilbors-0/+10
fix: Build and run build scripts in lsif command
2024-08-12Build and run build scripts in lsif commandLukas Wirth-0/+10
2024-08-09Use Sender instead of boxed closure in vfsmo8it-2/+1
2024-08-06Replace `[package.repository] = "…"` of published crates with ↵Vincent Esche-1/+1
`[package.repository.workspace] = true`
2024-08-06Unify package descriptions by adding references to "rust-analyzer"Vincent Esche-1/+1
With the lack of a README on the individually published library crates and the somewhat cryptic `ra_ap_` prefix it is hard to figure out where those crates belong to, so mentioning "rust-analyzer" feels like auseful hint there.
2024-08-06Add repository URL for published crates' missing `[package.repository]` fieldsVincent Esche-0/+1
2024-08-06Replace `"TBD"` with more helpful desciptions in published crates' ↵Vincent Esche-1/+1
`[package.description]` fields
2024-08-05Auto merge of #17771 - Veykril:parallel-vfs-config, r=Veykrilbors-3/+7
internal: Load VFS config changes in parallel Simple attempt to make some progress f or https://github.com/rust-lang/rust-analyzer/issues/17373 No clue if those atomic orderings are right, though I don't think they are really too relevant either. A more complete fix would probably need to replace our `ProjectFolders` handling a bit.
2024-08-05feat: Load sysroot library via cargo metadataLukas Wirth-2/+2
2024-08-02internal: Load VFS config changes in parallelLukas Wirth-3/+7
2024-07-26Internal: Cleanup proc-macro error handlingLukas Wirth-8/+10
2024-07-23minor changesAli Bektas-6/+8
2024-07-22Read rust-analyzer.toml files on startupAli Bektas-8/+27
2024-07-19Auto merge of #17639 - Veykril:salsa-perf, r=Veykrilbors-1/+1
Some more small salsa memory improvements This does limit our lru limits to 2^16 but if you want to set them higher than that you might as well not set them at all. Also makes `LRU` opt-in per query now, allowing us to drop all the unnecessary LRU stuff for most queries
2024-07-19Reduce maximum LRU size to 2^16 entries, reducing memory footprint of LRU ↵Lukas Wirth-1/+1
entries
2024-07-18feature: move `linked_projects` discovery to the rust-analyzer serverDavid Barsky-2/+0
2024-07-16Remove Name::to_smol_strLukas Wirth-3/+9