aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* force serde in ra_syntaxAleksey Kladov2019-01-114-11/+26
|
* Merge #489bors[bot]2019-01-109-204/+448
|\ | | | | | | | | | | | | | | 489: support std r=matklad a=matklad closes #465 Co-authored-by: Aleksey Kladov <[email protected]>
| * install rust-src component on CIAleksey Kladov2019-01-101-0/+1
| |
| * minorAleksey Kladov2019-01-102-6/+2
| |
| * wire sysroot into crate graphAleksey Kladov2019-01-104-37/+95
| |
| * special case stdAleksey Kladov2019-01-101-2/+6
| |
| * use arena for sysrootAleksey Kladov2019-01-102-50/+90
| |
| * split moduleAleksey Kladov2019-01-103-241/+261
| |
| * add sysroot boilerplateAleksey Kladov2019-01-106-32/+157
|/
* Merge #490bors[bot]2019-01-104-4/+1
|\ | | | | | | | | | | | | | | 490: dont depend on tools from lsp-server r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * dont depend on tools from lsp-serverAleksey Kladov2019-01-104-4/+1
| |
* | Merge #463bors[bot]2019-01-107-16/+179
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 463: Use name resolution for goto definition r=matklad a=flodiebold This tries proper name resolution before falling back on the index. @matklad There was currently no way of getting the location of a `DefId` from outside `ra_hir`. I added something, but it's probably not the best API, maybe you have a better idea? Co-authored-by: Florian Diebold <[email protected]>
| * | Use name resolution for goto definitionFlorian Diebold2019-01-107-16/+179
|/ /
* | Merge #470bors[bot]2019-01-1012-46/+205
|\ \ | |/ |/| | | | | | | | | | | | | | | 470: Type inference for enum variants r=flodiebold a=marcusklaas Opened a new PR instead of https://github.com/rust-analyzer/rust-analyzer/pull/461. Totally botched that one. I think I resolved all the issues mentioned there. Co-authored-by: Marcus Klaas de Vries <[email protected]>
| * Save variant names in EnumData to reduce needless queriesMarcus Klaas de Vries2019-01-104-39/+25
| | | | | | | | | | | | We already have their names when anyway, and when in all (current) situations where we're interested in an Enum's variants, we want their names.
| * Implement type inference for enum variantsMarcus Klaas de Vries2019-01-1012-45/+218
| |
* | Merge #488bors[bot]2019-01-103-30/+28
|\ \ | | | | | | | | | | | | | | | | | | | | | 488: switch CargoWorkspace to arena r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | switch CargoWorkspace to arenaAleksey Kladov2019-01-103-30/+28
| | |
* | | Merge #487bors[bot]2019-01-104-6/+26
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 487: dont complete () if they are already there r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | dont complete () if they are already thereAleksey Kladov2019-01-104-6/+26
|/ / /
* | | Merge #486bors[bot]2019-01-103-0/+68
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | 486: Fix handling of where clauses in tuple structs r=matklad a=DJMcNab Originally reported by @max-frai on discord. As I was writing this, I was wondering if there's any way we can compare our test suite against libsyntax (i.e. check that it similarly fails/succeeds). Any ideas? Co-authored-by: DJMcNab <[email protected]>
| * | Fix handling of where clauses in tuple structsDJMcNab2019-01-103-0/+68
|/ /
* | Merge #483bors[bot]2019-01-101-10/+59
|\ \ | | | | | | | | | | | | | | | | | | | | | 483: better change visibility assist r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | better change visibility assistAleksey Kladov2019-01-101-10/+59
|/ / | | | | | | | | * don't add visibility before #derive * suggest changing pub(crate) into pub
* | Merge #482bors[bot]2019-01-105-507/+510
|\ \ | | | | | | | | | | | | | | | | | | | | | 482: fix code duplication r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | fix code duplicationAleksey Kladov2019-01-104-68/+55
| | |
| * | move join_lines to a separate moduleAleksey Kladov2019-01-103-487/+503
| |/
* | Merge #481bors[bot]2019-01-104-1/+118
|\ \ | |/ |/| | | | | | | | | | | 481: introduce marking infrastructure for maintainable tests r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * introduce marking infrastructure for maintainable testsAleksey Kladov2019-01-104-1/+118
|/ | | | This also fixes a particular edge case in name resolution.
* Merge #475bors[bot]2019-01-106-59/+99
|\ | | | | | | | | | | | | | | | | | | | | 475: Show types of fields in completion r=matklad a=matklad ![image](https://user-images.githubusercontent.com/1711539/50910524-0f146200-143f-11e9-84d6-0ba80761cd89.png) r? @flodiebold Co-authored-by: Aleksey Kladov <[email protected]>
| * show field types in completionAleksey Kladov2019-01-095-61/+88
| |
| * add completion detailAleksey Kladov2019-01-092-0/+13
| |
* | Merge #478bors[bot]2019-01-108-48/+87
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 478: WIP: implement cancelation via unwinding r=matklad a=matklad This uses https://github.com/salsa-rs/salsa/pull/107 to implement cancellation. Now we can get rid of `Cancelable` wrapper from everywhere except the top-level analyzer library. Co-authored-by: Aleksey Kladov <[email protected]>
| * | upgrade salsaAleksey Kladov2019-01-101-1/+1
| | |
| * | explain why we use resume_unwindAleksey Kladov2019-01-101-0/+2
| | |
| * | implement RefUnwindSafeAleksey Kladov2019-01-104-6/+16
| | |
| * | use unwinding for cancelationAleksey Kladov2019-01-106-43/+61
| | |
| * | unwind on cancelAleksey Kladov2019-01-093-11/+20
| |/
* | Merge #477bors[bot]2019-01-101-4/+127
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | 477: Extend selection for list items r=matklad a=hban First PR, criticism welcome! There are a few things I'm not so sure about: * There is now a not-so-small list of "list-like kinds" in extend selection source which maybe should belong somewhere else. * Preferring left comma doesn't seem right IMO for one reason - trailing commas are usually on the right. For example, when array values are broken across multiple lines extending selected value will cover right trailing comma (because it's the only comma on the same line), but when all values are on the same line it will pick left comma. Anyway, currently with this PR it will pick always extend to left comma when possible since that's what issue specified 😃. Closes: #444 Co-authored-by: Hrvoje Ban <[email protected]>
| * Extend selection for list itemsHrvoje Ban2019-01-091-4/+127
|/
* Merge #476bors[bot]2019-01-095-15/+21
|\ | | | | | | | | | | | | | | 476: nicer trailing comma handling in types r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * nicer trailing comma handling in typesAleksey Kladov2019-01-095-15/+21
|/
* Merge #474bors[bot]2019-01-092-4/+4
|\ | | | | | | | | | | | | | | 474: Fix rev to deleted branch r=matklad a=weiznich Co-authored-by: Georg Semmler <[email protected]>
| * Fix rev to deleted branchGeorg Semmler2019-01-092-4/+4
|/
* Merge #473bors[bot]2019-01-0928-112/+171
|\ | | | | | | | | | | | | | | 473: Partial typo fix r=matklad a=marcusklaas This fixes some typos. Mostly in documentation, but also some code is affected (`defenition` was used in a few method names). Co-authored-by: Marcus Klaas de Vries <[email protected]>
| * Fix typos in ARCHITECTURE.md and a number of cratesMarcus Klaas de Vries2019-01-0923-91/+150
| | | | | | | | specifically: gen_lsp_server, ra_arena, ra_cli, ra_db, ra_hir
| * Fix typo defenition -> definitionMarcus Klaas de Vries2019-01-088-21/+21
| |
* | Merge #472bors[bot]2019-01-083-93/+103
|\ \ | |/ |/| | | | | | | | | | | 472: Stupidly simple idea to make DefIds more stable r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * fuzz-lockfileAleksey Kladov2019-01-081-32/+9
| |
| * more stable DefIds via bfs tree walkingAleksey Kladov2019-01-082-7/+31
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-02 01:01:31 +0000