aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_lsp_server
Commit message (Collapse)AuthorAgeFilesLines
* Add alloc to std depsFlorian Diebold2019-02-041-0/+1
|
* Future proof by explicitly matching against Nonekjeremy2019-02-041-1/+1
|
* Add commentkjeremy2019-02-041-0/+4
|
* Implement lens for impls and support resolving lenses.Jeremy Kolb2019-02-043-3/+85
|
* Add core to STD_DEPSLaurențiu Nicola2019-02-031-0/+1
| | | See #731.
* Use the new Resolver API in completionFlorian Diebold2019-02-011-0/+1
|
* formatJeremy Kolb2019-01-311-1/+3
|
* Use "▶" for test code lensJeremy Kolb2019-01-311-1/+1
| | | | I find that this makes code lenses stand out more.
* Merge #702bors[bot]2019-01-304-3/+24
|\ | | | | | | | | | | | | | | | | 702: Go to Implementation r=matklad a=kjeremy First half of #620 Co-authored-by: Jeremy Kolb <[email protected]> Co-authored-by: kjeremy <[email protected]>
| * Go to Implementation for structs and enumsJeremy Kolb2019-01-304-3/+24
| |
* | Pass Documentation up to LSP and add "rust" to our codeblocks thereJeremy Kolb2019-01-304-15/+54
|/
* opt-in jemallocAleksey Kladov2019-01-281-0/+3
|
* align command namingAleksey Kladov2019-01-283-14/+14
|
* automatically collect garbageAleksey Kladov2019-01-272-2/+7
|
* Don't use the reserved error codeDJMcNab2019-01-261-1/+1
|
* Return an lsp errorDJMcNab2019-01-261-5/+8
|
* Use the correct working directory for cargo metadata and rustfmtDJMcNab2019-01-262-7/+20
|
* Fold blocks of mod items.Andrea Pretto2019-01-251-0/+1
| | | | Fixes #572
* add gc requestAleksey Kladov2019-01-253-9/+30
|
* Fill in DocumentSymbol::detailHrvoje Ban2019-01-241-1/+1
|
* Fix target_selection_range typeHirokazu Hata2019-01-231-1/+1
|
* Bumpup lsp-types to v0.55.0Hirokazu Hata2019-01-231-1/+1
|
* ad status commandAleksey Kladov2019-01-224-0/+28
|
* Teach CompletionItem about documentationJeremy Kolb2019-01-221-2/+10
|
* Merge #574bors[bot]2019-01-202-17/+27
|\ | | | | | | | | | | | | | | | | 574: refactor completions to use TextEdit instead of InsertText r=matklad a=gfreezy 1. migrate from `insertText` to `TextEdit` from `CompleteItem` 2. use `insta` to test completions Co-authored-by: gfreezy <[email protected]>
| * use a combination of `source_change` and `text_edit` for `CompleteItem`gfreezy2019-01-201-7/+4
| |
| * refactor to use `remove_range` and `replace_range` instead of TextEditgfreezy2019-01-191-7/+13
| |
| * refactor completions to use TextEdit instead of InsertTextgfreezy2019-01-192-17/+24
| |
* | extend selection expands macros and can totally panicAleksey Kladov2019-01-201-4/+8
| |
* | somewhat better nameAleksey Kladov2019-01-201-1/+1
| |
* | make matching brace consistentAleksey Kladov2019-01-201-2/+1
|/
* more idiomatic codegfreezy2019-01-191-5/+6
|
* fix commentsgfreezy2019-01-191-31/+3
|
* rename modgfreezy2019-01-192-20/+32
|
* :arrow_up: update rustAleksey Kladov2019-01-192-2/+0
|
* update cargo_metadataAleksey Kladov2019-01-142-3/+6
|
* switch to lsp-typesAleksey Kladov2019-01-149-24/+24
|
* target_selection_range is not nullable in the implementationAleksey Kladov2019-01-131-5/+10
|
* Merge #517 #518bors[bot]2019-01-131-4/+21
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 517: gracefully handle cycles in crate graph r=matklad a=matklad 518: Add an explanatory message when we use the Query fallback r=matklad a=DJMcNab Fixes https://github.com/rust-analyzer/rust-analyzer/issues/269. There is no good way to explain it for go_to_def, so I've just fallen back on to_vec. Co-authored-by: Aleksey Kladov <[email protected]> Co-authored-by: DJMcNab <[email protected]>
| * gracefully handle cycles in crate graphAleksey Kladov2019-01-131-4/+21
| | | | | | | | | | rust-lang/rust has absolutely weird setup with rustc-workspace-shim, which leads to real cycles.
* | Add bench runnable and code lensJeremy Kolb2019-01-122-35/+48
|/
* Merge #505bors[bot]2019-01-121-0/+1
|\ | | | | | | | | | | | | | | | | | | 505: Inherent methods r=matklad a=flodiebold This adds resolution, type checking and completion for inherent methods. The main open question here is the caching, I think. I'm not sure whether we should be caching method resolutions in a more fine grained way (currently we just build a hash map of types -> impl blocks, and iterate through all potential impl blocks when looking for a method). Co-authored-by: Florian Diebold <[email protected]>
| * Complete inherent methodsFlorian Diebold2019-01-121-0/+1
| |
* | Merge #500bors[bot]2019-01-126-99/+154
|\ \ | |/ |/| | | | | | | | | | | | | | | | | 500: Code lens support for running tests r=matklad a=kjeremy Supports running individual and mod tests. I feel like this kind of abuses the `Runnables` infrastructure but it works. Maybe later on down the line we should introduce a struct that is really just a tuple of binary, arguments, and environment and pass that back to the client instead. `run_single.ts` is just a paired down version of `runnables.ts` and there is duplication because I think run_single will probably change independent of runnables. Co-authored-by: Jeremy A. Kolb <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * Move `CargoTargetSpec` and friends to cargo_target_spec moduleJeremy Kolb2019-01-123-90/+102
| |
| * Code lens support for running testsJeremy A. Kolb2019-01-114-85/+128
| |
* | Switch hover to use MarkupContentJeremy Kolb2019-01-121-2/+5
| | | | | | | | MarkedString is deprecated
* | warn louder on mising sysrootAleksey Kladov2019-01-112-1/+9
|/
* actually produce missing def kindsAleksey Kladov2019-01-111-0/+4
|
* Merge #496bors[bot]2019-01-112-9/+35
|\ | | | | | | | | | | | | | | 496: Include two element ranges into the nav. r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 22:39:59 +0000