aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
* migrate ra_fmt to new rowanAleksey Kladov2019-07-191-7/+7
|
* migrate mbe to the new rowanAleksey Kladov2019-07-194-36/+27
|
* migrate ra_syntax to the new rowan APIAleksey Kladov2019-07-1918-2347/+1183
|
* use Parse in mbeAleksey Kladov2019-07-187-63/+64
|
* make Parse genericAleksey Kladov2019-07-185-23/+44
|
* Merge #1547bors[bot]2019-07-182-6/+5
|\ | | | | | | | | | | | | | | 1547: cleanup imports r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * cleanup importsAleksey Kladov2019-07-182-6/+5
| |
* | prettier colorsAleksey Kladov2019-07-183-18/+21
|/
* Merge #1537bors[bot]2019-07-181-26/+103
|\ | | | | | | | | | | | | | | | | | | | | | | 1537: Less magic completions r=matklad a=marcogroppo Restrict `if`, `not` and `while` postfix magic completions to boolean expressions and expressions of an unknown type. (this may be controversial, marking as draft for this reason) See the discussion in #1526. Co-authored-by: Marco Groppo <[email protected]>
| * Restrict some postfix completions to bool and unknown expr.Marco Groppo2019-07-171-26/+103
| | | | | | | | | | Restrict `if` and `while` postfix completions to boolean expressions and expressions of an unknown type.
* | highlight mutable variables differentlyEkaterina Babshukova2019-07-185-55/+104
| |
* | use more correct phantom types for ptrsAleksey Kladov2019-07-182-2/+2
| |
* | jemallocator 0.3Jeremy A. Kolb2019-07-172-5/+5
| |
* | Add "Run" lens for binary runnablesKirill Bulatov2019-07-161-1/+1
|/
* cargo updatekjeremy2019-07-152-2/+2
|
* Switch to Chalk master, without fuelFlorian Diebold2019-07-152-4/+4
|
* Remove blacklist, instead mark `Sized` as non-enumerableFlorian Diebold2019-07-151-17/+3
| | | | | This seems to be enough to prevent hanging in rust-analyzer, Chalk and the rustc repo.
* Cargo update, including updating ChalkFlorian Diebold2019-07-141-0/+2
|
* Have InferenceContext contain an InferenceResult instead of duplicating all ↵Florian Diebold2019-07-141-36/+19
| | | | fields
* Some renamings for clarityFlorian Diebold2019-07-149-25/+28
|
* Fixed request commentsAlexander Andreev2019-07-142-66/+72
|
* Fixed commentsAlexander Andreev2019-07-131-2/+2
|
* More resolution modules with attribute pathAlexander Andreev2019-07-132-4/+521
| | | | #1211
* complete fields in enum variantsEkaterina Babshukova2019-07-125-16/+116
|
* make Parse fields privateAleksey Kladov2019-07-1231-99/+109
| | | | this is in preparation for the new rowan API
* Merge #1523bors[bot]2019-07-122-0/+11
|\ | | | | | | | | | | | | | | 1523: account for dependencies when showing memory usage r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * account for dependencies when showing memory usageAleksey Kladov2019-07-122-0/+11
| |
* | Merge #1520bors[bot]2019-07-113-10/+15
|\ \ | |/ |/| | | | | | | | | | | | | | | 1520: Ignore workspace/didChangeConfiguration notifications. r=matklad a=bolinfest If the client happens to send a `workspace/didChangeConfiguration` notification, it is nicer if rust-analyzer can just ignore it rather than crash with an "unhandled notification" error. Co-authored-by: Michael Bolin <[email protected]>
| * Remove executeCommandProvider: apply_code_action.Michael Bolin2019-07-112-10/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This appears to have been introduced ages ago in https://github.com/rust-analyzer/rust-analyzer/commit/be742a587704f27f4e503c50f549aa9ec1527fcc but has since been removed. As it stands, it is problematic if multiple instances of the rust-analyzer LSP are launched during the same VS Code session because VS Code complains about multiple LSP servers trying to register the same command. Most LSP servers workaround this by parameterizing the command by the process id. For example, this is where `rls` does this: https://github.com/rust-lang/rls/blob/ff0b9057c8f62bc4f8113d741e96c9587ef1a817/rls/src/server/mod.rs#L413-L421 Though `apply_code_action` does not seems to be used, so it seems better to delete it than to parameterize it.
| * Ignore workspace/didChangeConfiguration notifications.Michael Bolin2019-07-112-4/+11
| |
* | move whitespace manipulation inside AstEditorEkaterina Babshukova2019-07-102-19/+17
| |
* | Make clippy a bit happierPascal Hertleif2019-07-101-0/+4
| | | | | | | | | | Random drive-by fix. I honestly blame rust-analyzer itself on this, because I set its watch mode to use `cargo clippy` :shrug:
* | Resolve a FIXMEPascal Hertleif2019-07-101-3/+1
|/ | | | Now that we are using a newer smol_str release this can be simplified :)
* fix profile nameAleksey Kladov2019-07-091-1/+1
|
* Merge #1515bors[bot]2019-07-0911-119/+286
|\ | | | | | | | | | | | | | | | | | | | | | | 1515: Trait environment r=matklad a=flodiebold This adds the environment, i.e. the set of `where` clauses in scope, when solving trait goals. That means that e.g. in ```rust fn foo<T: SomeTrait>(t: T) {} ``` , we are able to complete methods of `SomeTrait` on the `t`. This affects the trait APIs quite a bit (since every method that needs to be able to solve for some trait needs to get this environment somehow), so I thought I'd do it rather sooner than later ;) Co-authored-by: Florian Diebold <[email protected]>
| * Unify `normalize` and `implements` to simplify codeFlorian Diebold2019-07-089-107/+67
| |
| * Use environment for associated type normalization as wellFlorian Diebold2019-07-087-20/+52
| |
| * Start handling environment in trait resolutionFlorian Diebold2019-07-086-14/+103
| | | | | | | | | | I.e. if we are inside a function with some where clauses, we assume these where clauses hold.
| * Refactor a bit & introduce Environment structFlorian Diebold2019-07-087-21/+107
| |
* | Merge #1512bors[bot]2019-07-093-17/+106
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 1512: Infer ? operator r=unrealhoang a=unrealhoang Logical continuation of https://github.com/rust-analyzer/rust-analyzer/pull/1501 cc https://github.com/rust-analyzer/rust-analyzer/issues/1426 Co-authored-by: Unreal Hoang <[email protected]>
| * | beautify testsUnreal Hoang2019-07-091-20/+36
| | |
| * | use namespaced consts for KnownNameUnreal Hoang2019-07-081-12/+10
| | |
| * | projection over std::ops::Try::Ok to infer try/?Unreal Hoang2019-07-083-2/+77
| | |
* | | Look for the fXX_runtime lang items during method resolution.Marco Groppo2019-07-081-4/+6
| |/ |/|
* | Remove unused dependenciesShotaro Yamada2019-07-088-19/+0
|/
* don't send LocationLink unless the client opts-inAleksey Kladov2019-07-085-12/+62
| | | | closes #1474
* simplifyAleksey Kladov2019-07-082-23/+20
|
* add try_conv_with_to_vecAleksey Kladov2019-07-082-40/+54
|
* Merge #1504bors[bot]2019-07-084-38/+30
|\ | | | | | | | | | | | | | | 1504: Simplify LSP handlers r=matklad a=kjeremy Takes advantage of protocol inheritance via composition and simplifies some responses via the `From`/`Into` traits. Co-authored-by: Jeremy Kolb <[email protected]>
| * Simplify responses by using into()Jeremy Kolb2019-07-073-13/+14
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 09:47:23 +0000