aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge #6974bors[bot]2020-12-211-1/+1
|\ | | | | | | | | | | | | | | | | | | 6974: Stop setting CompletionItem::deprecated r=matklad a=lnicola Closes #2042 We're now using the `CompletionItem::tags` field to mark `CompletionItem`s as deprecated, and `CompletionItem::deprecated` is gone from LSP. Co-authored-by: Laurențiu Nicola <[email protected]>
| * Stop setting CompletionItem::deprecatedLaurențiu Nicola2020-12-211-1/+1
|/
* Merge #6965bors[bot]2020-12-217-147/+199
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6965: Properly attach attributes to Param instead of parent ParamList r=matklad a=Veykril Fixes #2783, fixes #2781 The problem with `let _a = [0,#[cfg(feature = "L")]0];` has already been fixed some time ago it seems: <details> <summary>Syntax Tree for the const item</summary> ``` [email protected] [email protected] "let" [email protected] " " [email protected] [email protected] [email protected] "_a" [email protected] " " [email protected] "=" [email protected] " " [email protected] [email protected] "[" [email protected] [email protected] "0" [email protected] "," [email protected] [email protected] [email protected] "#" [email protected] "[" [email protected] [email protected] [email protected] [email protected] "cfg" [email protected] [email protected] "(" [email protected] "feature" [email protected] " " [email protected] "=" [email protected] " " [email protected] "\"L\"" [email protected] ")" [email protected] "]" [email protected] "0" [email protected] "]" [email protected] ";" ``` </details> Co-authored-by: Lukas Wirth <[email protected]>
| * Parse attributes in tuple expressionsLukas Wirth2020-12-203-3/+56
| |
| * Properly attach attributes to Param instead of parent ParamListLukas Wirth2020-12-204-144/+143
| |
* | Merge #6967bors[bot]2020-12-214-9/+63
|\ \ | | | | | | | | | | | | | | | | | | | | | 6967: Correctly parse legacy trait objects with leading ForType r=matklad a=Veykril Fixes #1422 Co-authored-by: Lukas Wirth <[email protected]>
| * | Properly parse legacy trait objects with leading ForTypeLukas Wirth2020-12-204-9/+63
| |/
* | Merge #6968bors[bot]2020-12-201-4/+4
|\ \ | | | | | | | | | | | | | | | | | | | | | 6968: Update syn and quote r=kjeremy a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * | Update syn and quoteJeremy Kolb2020-12-201-4/+4
| | |
* | | Merge #6963bors[bot]2020-12-201-15/+27
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6963: Split lines between sentences r=lnicola a=lnicola bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | Split lines between sentencesLaurențiu Nicola2020-12-201-15/+27
| | | |
* | | | Merge #6961bors[bot]2020-12-201-1/+1
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6961: Document the version requirements for building from source r=lnicola a=lnicola Fixes #6667 bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | Document the version requirements for building from sourceLaurențiu Nicola2020-12-201-1/+1
| | | |
* | | | Merge #6959bors[bot]2020-12-203-2/+14
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6959: Use pattern_single instead of pattern in mbe pat r=jonas-schievink a=edwin0cheng Fix #6882 Co-authored-by: Edwin Cheng <[email protected]>
| * | | | Use pattern_single instead of pattern in mbe patEdwin Cheng2020-12-203-2/+14
| | |_|/ | |/| |
* | | | Merge #6921bors[bot]2020-12-205-19/+74
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 6921: Higher-ranked trait bounds for where clauses r=flodiebold a=Veykril There is a slight problem with this which is also noted in a FIXME now but `LifetimeParameters` of these ForLifetime where clauses allocate the lifetimes in the corresponding arena as if they were lifetimes of the item itself and not just the clause they belong to. I wasn't entirely sure what I could do about this but given nothing really uses lifetimes like that currently I figured it might be fine? Open to suggestions for that problem. Co-authored-by: Lukas Wirth <[email protected]>
| * | | Higher-ranked trait bounds for where clausesLukas Wirth2020-12-174-18/+74
| | | |
| * | | Remove obsolete FIXMELukas Wirth2020-12-171-1/+0
| | | |
* | | | Merge #6958bors[bot]2020-12-2022-102/+88
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6958: Align code_model name with ungrammar r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Align code_model name with ungrammarAleksey Kladov2020-12-2022-102/+88
|/ / / /
* | | | Merge #6929bors[bot]2020-12-204-3/+18
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | 6929: Handle $_ in mbe r=edwin0cheng a=lnicola Fixes #6926 Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | mbe: treat _ as identLaurențiu Nicola2020-12-204-3/+18
| | | |
* | | | Merge #6954bors[bot]2020-12-191-10/+10
|\ \ \ \ | | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | 6954: cargo update r=kjeremy a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * | | cargo updateJeremy Kolb2020-12-191-10/+10
| | | |
* | | | Merge #6953bors[bot]2020-12-191-0/+35
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 6953: Add test_rename_bind_pat r=bjorn3 a=bjorn3 Fixes #2976 Co-authored-by: bjorn3 <[email protected]>
| * | | Add test_rename_bind_patbjorn32020-12-191-0/+35
| | | |
* | | | Merge #6946bors[bot]2020-12-1912-216/+263
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6946: Better fuzzy heuristics r=matklad a=SomeoneToIgnore Continuation of the https://github.com/rust-analyzer/rust-analyzer/pull/6922, mainly created for a test. Turns out our current completions tests were sorting the completions by label, I had to remove that to test the order properly and update this order in a bunch of tests (ergo the changes) Co-authored-by: Kirill Bulatov <[email protected]>
| * | | Fewer allocationsKirill Bulatov2020-12-191-5/+7
| | | |
| * | | Tidy upKirill Bulatov2020-12-192-32/+26
| | | |
| * | | Keep the original completion order in testsKirill Bulatov2020-12-1912-194/+193
| | | |
| * | | Add a slightly better fuzzy search heuristicsKirill Bulatov2020-12-191-10/+62
| | | |
* | | | Merge #6951bors[bot]2020-12-196-36/+39
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6951: Make sure that HighlightModifier::ALL is synchronized with enum r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Make sure that HighlightModifier::ALL is synchronized with enumAleksey Kladov2020-12-196-36/+39
|/ / / /
* | | | Merge #6948bors[bot]2020-12-191-23/+55
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6948: Add API for mapping `Attr` back to its syntax node r=jonas-schievink a=jonas-schievink This will be useful for emitting diagnostics pertaining to a specific attribute Co-authored-by: Jonas Schievink <[email protected]>
| * | | | Add API for mapping `Attr` back to its syntax nodeJonas Schievink2020-12-191-23/+55
| |/ / /
* | | | Merge #6949bors[bot]2020-12-194-15/+14
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6949: Clarify the meaning of no-op highlight tag r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Clarify the meaning of no-op highlight tagAleksey Kladov2020-12-194-15/+14
| | | | |
* | | | | Merge #6947bors[bot]2020-12-198-47/+69
|\| | | | | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 6947: Use more Rustic highlighting specifiers r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Use more Rustic highlighting specifiersAleksey Kladov2020-12-198-47/+69
|/ / / | | | | | | | | | | | | *Method* works for OO languages, but in rust we can also have associated constants & types, so let's move this to a modifier.
* | | Merge #6944bors[bot]2020-12-191-14/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6944: Make attribute API more private r=jonas-schievink a=jonas-schievink bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | Make `RawAttrs` crate-privateJonas Schievink2020-12-191-2/+2
| | | | | | | | | | | | | | | | There should be no need to use this from outside
| * | | Remove `Attrs::merge`Jonas Schievink2020-12-191-12/+0
|/ / / | | | | | | | | | Only the `RawAttrs` version of this is in use
* | | Merge #6943bors[bot]2020-12-191-1/+0
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6943: Remove resolved FIXME r=jonas-schievink a=jonas-schievink bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | Remove resolved FIXMEJonas Schievink2020-12-191-1/+0
|/ / /
* | | Merge #6942bors[bot]2020-12-196-33/+66
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6942: Minor `#[derive]` resolution cleanup r=jonas-schievink a=jonas-schievink bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | fixture -> ra_fixtureJonas Schievink2020-12-192-4/+4
| | | |
| * | | Test paths to derive macrosJonas Schievink2020-12-191-2/+2
| | | |
| * | | More accurate `#[derive]` parsingJonas Schievink2020-12-194-27/+60
|/ / / | | | | | | | | | This now allows full paths to the derive macro
* | | Merge #6937bors[bot]2020-12-186-124/+128
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6937: Deduplicate highlight tags and symbol kinds r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Deduplicate highlight tags and symbol kindsAleksey Kladov2020-12-186-124/+128
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Curiously, LSP uses different enums for those, and unsurprising and annoyingly, there are things which exist in one but not in the other. Let's not repeat the mistake and unify the two things
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-25 14:35:02 +0000