aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | Store macro invocation parameters as text instead of ttLaurențiu Nicola2020-07-225-13/+20
| | | | |
* | | | | Merge #5501bors[bot]2020-07-231-16/+16
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5501: minor r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | minorAleksey Kladov2020-07-231-16/+16
|/ / / /
* | | | Merge #5492bors[bot]2020-07-223-4/+24
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | 5492: Use symbol tags r=matklad a=kjeremy Currently the only spec'd tag is "deprecated". Co-authored-by: kjeremy <[email protected]>
| * | | Move deprecated attribute to where it is neededkjeremy2020-07-221-2/+6
| | | |
| * | | Use symbol tagskjeremy2020-07-223-4/+20
|/ / /
* | | Merge #5488bors[bot]2020-07-221-2/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5488: Update manual.adoc r=matklad a=Veetaha Co-authored-by: Veetaha <[email protected]>
| * | | Update manual.adocVeetaha2020-07-221-2/+2
| | | |
* | | | Merge #5489bors[bot]2020-07-221-3/+5
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 5489: Clarify initializationOptions r=matklad a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * | | Clarify initializationOptionsJeremy Kolb2020-07-221-3/+5
|/ / /
* | | Merge #5481bors[bot]2020-07-223-15/+40
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | 5481: Track document versions in the server r=kjeremy a=kjeremy This also pushes diagnostics for the correct file version on close so that when it is reopened stale diagnostics are not shown. Closes #5452 Co-authored-by: kjeremy <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * | 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
| |/ /
* | | Merge #5487bors[bot]2020-07-2211-119/+13
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5487: Setup global allocator in the correct crate r=matklad a=matklad It worked before, but was roundabout bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Setup global allocator in the correct crateAleksey Kladov2020-07-225-10/+6
| | | | | | | | | | | | | | | | It worked before, but was roundabout
| * | | Remove support for jemallocAleksey Kladov2020-07-2210-109/+7
|/ / / | | | | | | | | | | | | 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
| | | |
* | | | Merge #5479bors[bot]2020-07-223-10/+19
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5479: Allow gathering memory stats on non-jemalloc Linux r=matklad a=jonas-schievink I could also parse `/proc/$PID/statm` to get the resident set size, but decided against that for now as it isn't terribly useful. Note that `mallinfo()` is incredibly slow for some reason, and unfortunately this will be exposed to users via the "Memory Usage" command (even worse, the opened document will show the outdated values while the server is processing). So, not very ideal, but it keeps me from recompiling r-a with different feature sets all the time. Co-authored-by: Jonas Schievink <[email protected]>
| * | | | Allow gathering memory stats on non-jemalloc LinuxJonas Schievink2020-07-213-10/+19
| |/ / /
* | | | Merge #5483bors[bot]2020-07-211-3/+3
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 5483: bump crossbeam-channel r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * | | bump crossbeam-channelkjeremy2020-07-211-3/+3
|/ / /
* | | 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
| |/
* | Merge pull request #5447 from jethrogb/gitattributesAleksey Kladov2020-07-211-0/+4
|\ \ | | | | | | Update .gitattributes
| * | Update .gitattributesJethro Beekman2020-07-201-0/+4
| | | | | | | | | | | | See rust-lang/rust#57858
* | | Merge #5472bors[bot]2020-07-2110-5457/+5369
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5472: Replace insta with expect r=matklad a=lnicola Co-authored-by: LaurenČ›iu Nicola <[email protected]>
| * | | Remove insta depLaurențiu Nicola2020-07-214-92/+3
| | | |
| * | | Replace remaining insta usesLaurențiu Nicola2020-07-216-5365/+5366
|/ / /
| | |
| \ \
| \ \
| \ \
| \ \
| \ \
*-----. \ \ Merge #5451 #5463 #5465 #5466bors[bot]2020-07-2112-92/+141
|\ \ \ \ \ \ | |_|_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-202-11/+11
| | | |/ /
| | * / / Bump lexerkjeremy2020-07-202-3/+3
| | |/ /
| * | | 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]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 06:53:38 +0000