about summary refs log tree commit diff
path: root/crates
AgeCommit message (Collapse)AuthorLines
2022-04-14Improve ItemTree pretty print outputJonas Schievink-38/+50
2022-04-14add docsJonas Schievink-0/+3
2022-04-14reenable testJonas Schievink-31/+28
2022-04-14simplifyJonas Schievink-11/+5
2022-04-14Auto merge of #11985 - Veykril:config-valid, r=Veykrilbors-50/+96
minor: Simplify config.rs a bit
2022-04-14minor: Cleanup config.rs a bitLukas Wirth-50/+96
2022-04-14Auto merge of #11960 - Veykril:config-valid, r=Veykrilbors-51/+82
internal: Show more project building errors to the user Should help out with https://github.com/rust-analyzer/rust-analyzer/issues/9720 Fixes https://github.com/rust-analyzer/rust-analyzer/issues/11223
2022-04-14internal: Show more project building errors to the userLukas Wirth-51/+82
2022-04-13Update repo URLAlex Touchet-2/+2
2022-04-13Auto merge of #11956 - fee1-dead:master, r=flodieboldbors-15/+35
feat: allow customizing the command for running build scripts I have tested this locally and it fixed #9201 with some small changes on the compiler side with suggestions from https://github.com/rust-analyzer/rust-analyzer/issues/9201#issuecomment-1019554086. I have also added an environment variable `IS_RA_BUILDSCRIPT_CHECK` for crates to detect that it is a check for buildscripts, and allows defaulting to bogus values for expected environment variables.
2022-04-13Update CI for Rust borsDeadbeef-1/+1
2022-04-13Remove trailing `;` when turning assignment into `==` comparisonJonas Schievink-1/+70
2022-04-13Add more no-op testsJonas Schievink-0/+16
2022-04-13feat: allow customizing the command for running build scriptsDeadbeef-15/+35
2022-04-12Add trailing `;` when typing `=` in assignmentJonas Schievink-9/+95
2022-04-12Bump chalkLaurențiu Nicola-3/+3
2022-04-12Add trailing `;` when completing assoc const/typeJonas Schievink-15/+25
2022-04-12Merge #11967bors[bot]-22/+22
11967: fix: Fix trait impl completions not triggering after `fn`/`const`/`type` r=jonas-schievink a=jonas-schievink ![screenshot-2022-04-12-17:13:01](https://user-images.githubusercontent.com/1786438/162996087-56540f5e-a6be-4111-a4a5-8de21f483a5e.png) Fixes https://github.com/rust-analyzer/rust-analyzer/issues/11467 cc https://github.com/rust-analyzer/rust-analyzer/issues/11860 bors r+ Co-authored-by: Jonas Schievink <jonas.schievink@ferrous-systems.com>
2022-04-12Fix trait impl completions' `lookup_by` textJonas Schievink-22/+22
2022-04-12Merge #11883bors[bot]-13/+106
11883: fix(ide): move moudle directory when rename r=rainy-me a=rainy-me fix: #10992 Added `FileSystemEdit::MoveDir` variant for move dirs. Original implemented as recursively move child mod files but had many issues like 1. left empty dir after rename file 2. only affect rust file 3. not performant so changed to current version Co-authored-by: rainy-me <github@yue.coffee>
2022-04-12fix: move dir on rename modrainy-me-13/+106
2022-04-12simplifyJonas Schievink-4/+4
2022-04-11Merge #11964bors[bot]-2/+26
11964: internal: Show more project building errors to the user r=Veykril a=Veykril Something very fishy is going on with the `rustc_workspace` handling, which caused this bug to only manifest in the `std` library but not other library crate... So there is either a bug there or just the fact that we seem to add duplicate dependencies (I think this is what we are doing with this right?) might be tripping something up somewhere. cc https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/Rust-analyzer.20use.20inside.20stdlib bors r+ Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
2022-04-12fix: Unset test feature in rustc source cratesLukas Wirth-2/+26
2022-04-11Deprioritize already-imported namesJonas Schievink-49/+119
2022-04-11Add simplistic config validationLukas Wirth-0/+13
2022-04-11Show config deseralization failures on start upLukas Wirth-61/+84
2022-04-11Merge #11935bors[bot]-86/+33
11935: feat: Switch to LSP inlay hints r=lnicola a=lnicola Co-authored-by: Laurențiu Nicola <lnicola@dend.ro>
2022-04-11fix panic on GATAlex Chi-8/+37
Signed-off-by: Alex Chi <iskyzh@gmail.com>
2022-04-10Merge #11951bors[bot]-35/+54
11951: minor: Simplify r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
2022-04-10SimplifyLukas Wirth-35/+54
2022-04-10Merge #11954bors[bot]-158/+245
11954: Parse `for<'a>` closure syntax r=Veykril a=Veykril Fixes https://github.com/rust-analyzer/rust-analyzer/issues/11716 Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
2022-04-10Parse for<'a> closure syntaxLukas Wirth-158/+245
2022-04-10Merge #11953bors[bot]-165/+96
11953: fix: `extract_module` is too eager r=Veykril a=iDawer Refactored `extract_module`. Searching for usages and import resolving are done lazily. Close #11944 Co-authored-by: iDawer <ilnur.iskhakov.oss@outlook.com>
2022-04-09`extract_module`: Refactor loopsiDawer-84/+52
2022-04-09extract_module: Resolve imports lazilyiDawer-41/+27
2022-04-09Refactor `extract_module`iDawer-35/+20
2022-04-09Clean up `extract_module`iDawer-16/+8
2022-04-09Revert #11912 as it parses all visited filesLukas Wirth-16/+13
2022-04-09fix: Don't create `hir::Local`s from const path patternsLukas Wirth-2/+21
2022-04-09fix: Check whether a parameter can be converted to a localLukas Wirth-24/+41
2022-04-08Merge #11940bors[bot]-3/+11
11940: minor: bump lsp-server version r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
2022-04-09minor: bump lsp-server versionLukas Wirth-3/+11
2022-04-08Make trait item completions work in a bare impl and score themJonas Schievink-67/+139
2022-04-08Account for macros in `get_missing_assoc_items`Jonas Schievink-24/+34
2022-04-08Ignore `Drop` and `Destruct` bounds for nowFlorian Diebold-1/+97
- `T: ~const Drop` has a special meaning in Rust 1.61 that we don't implement. (So ideally, we'd only ignore `~const Drop`, but this should be fine for now.) - `Destruct` impls are built-in in 1.62 (current nightlies as of 08-04-2022), so until the builtin impls are supported by Chalk, we ignore them as well. Since `Destruct` is implemented for everything in non-const contexts IIUC, this should also work fine. Fixes #11932.
2022-04-08Switch to LSP inlay hintsLaurențiu Nicola-86/+33
2022-04-07flyimport: omit types when completing where-clauseJonas Schievink-2/+28
2022-04-07Merge #11920bors[bot]-56/+86
11920: Consider types of const generics r=flodiebold a=HKalbasi fix #11913 We should emit type_mismatch in const generics, probably after #7434. Currently they will lead to a misleading, time of use type error (like the added test). Co-authored-by: hkalbasi <hamidrezakalbasi@protonmail.com>
2022-04-07Determine function unsafety semanticallyJonas Schievink-98/+107