aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Update crates/rust-analyzer/src/main_loop.rsJeremy Kolb2020-07-221-1/+1
| | | | | | | | | Co-authored-by: Aleksey Kladov <[email protected]>
| * | Clear diagnostics for known file version on closekjeremy2020-07-211-3/+10
| | |
| * | Store document version and pass back to the clientkjeremy2020-07-213-13/+31
| | |
* | | Merge #5475bors[bot]2020-07-226-26/+270
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5475: Support `Trait as _` imports r=matklad a=jonas-schievink Fixes https://github.com/rust-analyzer/rust-analyzer/issues/2736 Co-authored-by: Jonas Schievink <[email protected]>
| * | | Check that visibility upgrade path is hitJonas Schievink2020-07-222-4/+8
| | | |
| * | | Support `Trait as _` importsJonas Schievink2020-07-216-26/+266
| |/ /
* | | Setup global allocator in the correct crateAleksey Kladov2020-07-224-9/+5
| | | | | | | | | | | | It worked before, but was roundabout
* | | Remove support for jemallocAleksey Kladov2020-07-225-23/+4
| | | | | | | | | | | | | | | We only used it for measuring memory usage, but now we can use glibc's allocator for that just fine
* | | Merge #5478bors[bot]2020-07-221-15/+75
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5478: Replace existing visibility modifier in fix_visibility r=matklad a=TimoFreiberg Fixes #4636 I would have liked to do something about the `// FIXME: this really should be a fix for diagnostic, rather than an assist.`, but that would take a while and there's no reason not to fix this immediately. Co-authored-by: Timo Freiberg <[email protected]>
| * | | Replace existing visibility modifier in fix_visibilityTimo Freiberg2020-07-211-15/+75
| | | |
* | | | Allow gathering memory stats on non-jemalloc LinuxJonas Schievink2020-07-212-10/+17
|/ / /
* | | Merge #5476bors[bot]2020-07-211-48/+55
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | 5476: Cleanup extact variable r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Cleanup extact variableAleksey Kladov2020-07-211-48/+55
| | |
| * | minorAleksey Kladov2020-07-211-2/+2
| |/
* | Remove insta depLaurențiu Nicola2020-07-212-3/+2
| |
* | Replace remaining insta usesLaurențiu Nicola2020-07-216-5365/+5366
| |
| |
| \
| \
| \
| \
| \
*-----. \ Merge #5451 #5463 #5465 #5466bors[bot]2020-07-2111-82/+131
|\ \ \ \ \ | |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5451: Highlight more cases of SyntaxKind when it is a punctuation r=matklad a=GrayJack This maybe closes #5406 Closes #5453 Separate what one expect to be a punctuation semantic token (like `,`, `;`, `(`, etc), and what is not (`&`, `::`, `+`, etc) 5463: Bump lexer r=matklad a=kjeremy Since we're now on rust 1.45 5465: Bump chalk r=matklad a=kjeremy 5466: Do not show default types in function and closure return values r=matklad a=SomeoneToIgnore Avoid things like <img width="522" alt="image" src="https://user-images.githubusercontent.com/2690773/87985936-1bbe4f80-cae5-11ea-9b8a-5383d896c296.png"> Co-authored-by: GrayJack <[email protected]> Co-authored-by: kjeremy <[email protected]> Co-authored-by: Kirill Bulatov <[email protected]>
| | | | * Do not show default types in closuresKirill Bulatov2020-07-202-3/+21
| | | | |
| | | * | Bump chalkkjeremy2020-07-201-3/+3
| | | |/
| | * / Bump lexerkjeremy2020-07-201-1/+1
| | |/
| * | On second thought, we want to preserve the textMate here where all ↵GrayJack2020-07-213-3/+5
| | | | | | | | | | | | punctuation that are from a Attr be highlited as Attribute
| * | `#` as AttributeGrayJack2020-07-213-2/+3
| | | | | | | | | | | | - Issue #5453
| * | @ as operatorGrayJack2020-07-211-2/+3
| | |
| * | Assingment semantic highlightGrayJack2020-07-206-41/+47
| | |
| * | Handle semantic highlight when STAR is part of the `*{const, mut}`GrayJack2020-07-206-32/+35
| | |
| * | Highlight more cases of SyntaxKind when it is a punctuationGrayJack2020-07-201-14/+32
| | |
* | | Merge #5467bors[bot]2020-07-212-0/+7
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5467: Allow null or empty values for configuration r=matklad a=kjeremy Allow the client to respond to `workspace/configuration` with `null` values. This is allowed per the spec if the client doesn't know about the configuration we've requested. This also protects against `null` or `{}` during initialize. I'm not sure if we want to interpret `{}` as "don't change anything" but I think that's a reasonable approach to take. This should help with LSP clients working out of the box. Fixes #5464 Co-authored-by: kjeremy <[email protected]>
| * | | Protect against `{}`kjeremy2020-07-201-1/+1
| | | |
| * | | Allow client to respond to workspace/configuration with null valueskjeremy2020-07-202-0/+7
| | |/ | |/| | | | | | | | | | This is allowed per the spec if the client doesn't know about the configuration we've requested.
* | | Merge #5471bors[bot]2020-07-212-5/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5471: Typo r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | TypoAleksey Kladov2020-07-212-5/+5
| | | |
* | | | Merge #5470bors[bot]2020-07-212-2/+11
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5470: Propagate cargo.target to checkOnSave r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Propagate cargo.target to checkOnSaveAleksey Kladov2020-07-212-2/+11
| |/ /
* | | Merge #5458bors[bot]2020-07-213-849/+896
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 5458: Use expect in some ra_hir_ty tests r=flodiebold a=lnicola Co-authored-by: LaurenČ›iu Nicola <[email protected]>
| * | Inline lang items in coercion testsLaurențiu Nicola2020-07-202-27/+65
| | |
| * | Use expect in never_type testsLaurențiu Nicola2020-07-203-186/+185
| | |
| * | Use expect in coercion testsLaurențiu Nicola2020-07-201-674/+684
| | |
* | | Merge #5440bors[bot]2020-07-207-8/+8
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5440: Minor perf tweaks per clippy r=matklad a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * | | Minor perf tweaks per clippyJeremy Kolb2020-07-197-8/+8
| | | |
* | | | SimplifyAleksey Kladov2020-07-201-9/+5
| | | |
* | | | Add is_workspace_member for rust-project.jsonAleksey Kladov2020-07-201-24/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is currently unused, but, in the future, it will be used to: * drive certain UX (symbols search by default will look only in the members) * improve performance (rust-analyzer will assume that non-members change rarely) If not specified, is_workspace member is inferred from the path
* | | | SimplifyAleksey Kladov2020-07-202-11/+11
| |_|/ |/| |
* | | Fix a typo in completion docsPascal Hertleif2020-07-191-1/+1
|/ /
* / Specify default adt representation for chalk integrationWilco Kusee2020-07-191-1/+1
|/
* Simplify exclusion logicAleksey Kladov2020-07-185-110/+120
|
* Don't show docs in concise signature helpAleksey Kladov2020-07-181-5/+9
|
* Add turbo-fish works after `()`Aleksey Kladov2020-07-181-1/+28
|
* Merge #5423bors[bot]2020-07-172-0/+102
|\ | | | | | | | | | | | | | | 5423: Correctly resolve assoc. types in path bindings r=matklad a=jonas-schievink Previously invoking goto def on `impl Iterator<Item<|> = ()>` would go to `Iterator`, not `Item`. This fixes that. Co-authored-by: Jonas Schievink <[email protected]>
| * Correctly resolve assoc. types in path bindingsJonas Schievink2020-07-172-0/+102
| |
* | More precise ranges in remove hashes assistAleksey Kladov2020-07-171-79/+52
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-01 09:56:08 +0000