aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* Fix assist test logicDaiki Ihara2020-12-211-2/+6
|
* Update test diagnostics in ideDaiki Ihara2020-12-211-0/+1
|
* Add initial_contents field for CreateFileDaiki Ihara2020-12-215-50/+47
|
* Add extract_module_to_file assistDaiki Ihara2020-12-213-0/+187
|
* Add handling file_system_edit in test assistsDaiki Ihara2020-12-212-15/+59
|
* 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
| |
* | 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 #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
| | | |
* | | | 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
| |/ / /
* | | | Clarify the meaning of no-op highlight tagAleksey Kladov2020-12-194-15/+14
| | | |
* | | | 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.
* | | 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
* | | Remove resolved FIXMEJonas Schievink2020-12-191-1/+0
| | |
* | | 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
* | | | Merge #6935bors[bot]2020-12-183-15/+28
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6935: Don't look at attributes when lowering to ItemTree r=jonas-schievink a=jonas-schievink Resolves 2 `cfg_attr` FIXMEs bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | | Don't look at attributes when lowering to ItemTreeJonas Schievink2020-12-183-15/+28
| |/ / / | | | | | | | | | | | | Resolves 2 `cfg_attr` FIXMEs
* | | | Merge #6934bors[bot]2020-12-186-3/+97
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 6934: Implement `cfg_attr` handling r=jonas-schievink a=jonas-schievink Part of https://github.com/rust-analyzer/rust-analyzer/issues/5548 Co-authored-by: Jonas Schievink <[email protected]>
| * | | Hit a markJonas Schievink2020-12-182-0/+5
| | | |
| * | | Add testJonas Schievink2020-12-181-0/+16
| | | |
| * | | Fix parsing of active cfg_attrJonas Schievink2020-12-181-2/+2
| | | |
| * | | Implement `RawAttr::filter`Jonas Schievink2020-12-185-3/+76
| | | |
* | | | Reduce test verbosityAleksey Kladov2020-12-183-597/+169
| | | |
* | | | NavTarget doesn't assume that it points to a symbolAleksey Kladov2020-12-187-81/+196
| | | |
* | | | Minor, cleanup APIAleksey Kladov2020-12-182-1/+4
| | | |
* | | | Don't expose SyntaxKind from IDE APIAleksey Kladov2020-12-1813-239/+337
| | | | | | | | | | | | | | | | | | | | | | | | SyntaxKind is somewhat of an internal type, but IDE is using it to basically specify an icon. Let's have a dedicated entity for this instead.
* | | | Cleaup importsAleksey Kladov2020-12-182-13/+13
|/ / / | | | | | | | | | ide should re-export everything it needs.
* / / Do not merge imports with different attributesJesse Bakker2020-12-182-1/+28
|/ /
* | Merge #6901bors[bot]2020-12-184-1/+22
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 6901: Temp fixes panic caused by no ast for proc-macro r=maklad a=edwin0cheng There are some panic when hover/goto definition for proc-macro. It is because in current design, we don't have `ast-node` for proc-macro and then it trigger [this](https://github.com/rust-analyzer/rust-analyzer/blob/479d1f7eec22c3564867223e2093f14774092528/crates/hir/src/has_source.rs#L116) line to panic. This PR is a temp fix for all of these similar to https://github.com/rust-analyzer/rust-analyzer/blob/bd4c352831662762ee7a66da77ec9adf623b0a0a/crates/completion/src/render/macro_.rs#L42 Co-authored-by: Edwin Cheng <[email protected]>
| * | Temp fixes panic caused by no ast for proc-macroEdwin Cheng2020-12-184-1/+22
| | |
* | | Refactor attributes API to allow handling cfg_attrJonas Schievink2020-12-188-114/+187
| | |
* | | Show first fuzzy completions fully containing the inputKirill Bulatov2020-12-171-5/+14
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-15 19:52:42 +0000