aboutsummaryrefslogtreecommitdiff
path: root/crates/project_model/src
Commit message (Collapse)AuthorAgeFilesLines
* Minor clippy perf fixesLaurențiu Nicola2021-06-181-1/+1
|
* clippy::redudant_borrowMaan20032021-06-134-10/+10
|
* clippy::redundant_clone fixesLaurențiu Nicola2021-05-262-8/+5
|
* Duplicate dependencies that have multiple DepKindsJonas Schievink2021-05-241-15/+21
|
* Add a FIXMEKirill Bulatov2021-05-241-0/+9
|
* Small file error display fixKirill Bulatov2021-05-241-1/+1
| | | Co-authored-by: Aleksey Kladov <[email protected]>
* Deal with todosKirill Bulatov2021-05-231-4/+14
|
* Drag detached files towards loadingKirill Bulatov2021-05-233-6/+72
|
* Draft detached files retrievalKirill Bulatov2021-05-232-0/+4
|
* Add more docsAleksey Kladov2021-05-223-6/+25
|
* Use package root as `cargo check` working directoryBrendan Cully2021-05-131-0/+1
| | | | | | | | | | | | | | | Cargo commands are affected by the `.cargo/config` files above their working directory. If cargo is invoked from above the directory holding `Cargo.toml`, it may not pick up important settings like registry replacements, causing it to behave differently or even fail. Most cargo invocations are currently setting their working directories to the directory containing `Cargo.toml`, but a couple of paths remain in which cargo is invoked from the default workspace root instead. This change fixes that, resolving some cargo check failures that I experienced in a multi-root workspace in which packages used different registries.
* Fix build script dependenciesJonas Schievink2021-05-122-12/+56
|
* Use Cargo target name as crate nameJonas Schievink2021-05-111-1/+4
|
* Use RUSTC_BOOTSTRAP=1 instead of +nightly when discovering rust_cfgs ↵Lukas Wirth2021-05-082-40/+35
| | | | throughs cargo
* Discover rustc_cfg through unstable cargo optionsLukas Wirth2021-05-083-33/+83
|
* internal: use API stabilized in 1.52Aleksey Kladov2021-05-061-2/+1
|
* fix: make error message in the status bar more usefulAleksey Kladov2021-04-261-1/+1
| | | | | | | At the moment,the popup is just a bazillion of Cargo's "Compiling this\nCompiling that", which is not that useful. --quiet still displays error, which is what we needc
* fix: no longer get stuck on windowsAleksey Kladov2021-04-201-58/+76
| | | | | | | reading both stdout & stderr is a common gotcha, you need to drain them concurrently to avoid deadlocks. Not sure why I didn't do the right thing from the start. Seems like I assumed the stderr is short? That's not the case when cargo spams `compiling xyz` messages
* feat: avoid checking the whole project during initial loadingAleksey Kladov2021-04-121-107/+129
|
* feat: show errors from `cargo metadata` and initial `cargo check` in the ↵Aleksey Kladov2021-04-061-2/+25
| | | | | | status bar closes #3155
* Clearer namingAleksey Kladov2021-04-062-29/+40
|
* internal: do not drop errors from cargo metadata/checkAleksey Kladov2021-04-061-1/+1
| | | | Work towards #3155
* clippy::complexity simplifications related to IteratorsMatthias Krüger2021-03-211-49/+42
|
* some clippy::performance fixesMatthias Krüger2021-03-151-1/+1
| | | | | | | use vec![] instead of Vec::new() + push() avoid redundant clones use chars instead of &str for single char patterns in ends_with() and starts_with() allocate some Vecs with capacity to avoid unneccessary resizing
* Never run cargo check on the rustc sourceDaniel McNab2021-03-081-4/+1
|
* Only show directory nameDaniel McNab2021-03-081-1/+1
|
* Revert "Support disabling rustc build scripts"Daniel McNab2021-03-081-10/+3
| | | | This reverts commit ddce6bb282764692d53b719bff4c37e3512d4556.
* Support disabling rustc build scriptsDaniel McNab2021-03-081-3/+11
|
* Fix the commentDaniel McNab2021-03-071-4/+4
| | | | It's worse than I thought...
* Extract the large nested block into a functionDaniel McNab2021-03-071-72/+98
| | | | | Also add some more detailed comments Extract into function deleted the previous comments
* Require opt in to rustc_privateDaniel McNab2021-03-072-70/+70
| | | | | | This gives the advantage that A future extension would be to check for `feature(rustc_private)` instead
* Don't double analyse the same crateDaniel McNab2021-03-071-1/+6
|
* Update crate graph to only use subcrates of rustc_driverDaniel McNab2021-03-071-38/+38
|
* If a manual dependency exists, don't overwriteDaniel McNab2021-03-061-1/+8
| | | | | | | | This is a hack to work around miri being included in our analysis of rustc-dev Really, we should probably use an include set of the actual root libraries I'm not sure how those are determined however
* Implement opt-in (and opt-out) rustc_privateDaniel McNab2021-03-062-3/+26
|
* Bump cargo_metadataLaurențiu Nicola2021-03-022-16/+16
|
* Fix a few clippy::perf warningskjeremy2021-02-161-1/+1
|
* Allow automatically detect the rustc-src directory (fixes #3517).Benjamin Bouvier2021-02-134-14/+54
| | | | | If the configured rustcSource is set to "discover", try to automatically detect a source from the sysroot rustc directory.
* Async Loading outdir and proc-macroEdwin Cheng2021-01-284-154/+235
|
* Make logger-based debugging more pleasantAleksey Kladov2021-01-281-2/+3
|
* Export `CARGO` for proc. macrosJonas Schievink2021-01-271-1/+4
|
* Use AbsPathEdwin Cheng2021-01-221-3/+3
|
* Refactor build script dataEdwin Cheng2021-01-224-196/+228
|
* Added defined_features in PackageDataEdwin Cheng2021-01-212-5/+8
|
* Avoid blocking the main loop when editing Cargo.tomlAleksey Kladov2021-01-183-61/+93
| | | | | | | | | | I've noticed a bunch of "main loop too long" warnings in console when typing in Cargo.toml. Profiling showed that the culprit is `rustc --print cfg` call. I moved it to the background project loading phase, where it belongs. This highlighted a problem: we generally use single `cfg`, while it really should be per crate.
* Add profile callAleksey Kladov2021-01-181-0/+1
|
* Add profile callAleksey Kladov2021-01-181-0/+3
|
* prepare to publish el libro de arenaAleksey Kladov2021-01-142-2/+2
|
* Use --workspace when loading extern resourcesChinedu Francis Nwafili2021-01-141-1/+1
| | | https://github.com/rust-analyzer/rust-analyzer/issues/5040#issuecomment-759853153
* Report progress for cargo metadata and output-dirEdwin Cheng2021-01-072-14/+34
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 18:20:10 +0000