aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
* | remove Cancelable from Module API, part 2Aleksey Kladov2019-01-157-33/+28
| |
* | remove Cancelable from Module APIAleksey Kladov2019-01-156-22/+18
| |
* | remove cancelable from symbolsAleksey Kladov2019-01-155-14/+12
| |
* | remove Cancelable from source bindersAleksey Kladov2019-01-1516-90/+68
| |
* | remove Cancelable from module_tree_queryAleksey Kladov2019-01-156-31/+28
| |
* | check_canceled does not return ResultAleksey Kladov2019-01-155-7/+19
| |
* | update salsaAleksey Kladov2019-01-155-6/+7
| |
* | Merge #546bors[bot]2019-01-1519-187/+425
|\ \ | | | | | | | | | | | | | | | | | | | | | 546: replace `assert_dbg_eq` with Insta r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | switch to insta for testingAleksey Kladov2019-01-1519-187/+425
| | |
* | | Merge #485bors[bot]2019-01-1419-130/+625
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 485: Add type inference for a bunch of primitives r=flodiebold a=marcusklaas This PR adds inference for `&str`, `&[u8]`, `char`, `bool`, floats and integers. For floats and integers it uses type variables to infer the exact type, i.e. `u32`, from context when it's not annotated explicitly. I'm not quite happy with the implementation yet, but I think it mostly works now. Co-authored-by: Marcus Klaas de Vries <[email protected]>
| * | | Address issues found in reviewMarcus Klaas de Vries2019-01-142-11/+9
| | | |
| * | | Fix type inference for raw (byte) stringsMarcus Klaas de Vries2019-01-146-21/+75
| | | |
| * | | Give literal expression default values for nowMarcus Klaas de Vries2019-01-141-23/+9
| | | |
| * | | Fixup testsMarcus Klaas de Vries2019-01-1412-211/+283
| | | |
| * | | Start moving literal interpretation to the AST (WIP)Marcus Klaas de Vries2019-01-144-10/+131
| | | |
| * | | don't try to treat arrays and tuples as literalsMarcus Klaas de Vries2019-01-145-57/+27
| | | |
| * | | Use type variables to determine exact type for ambiguous numeric literalsMarcus Klaas de Vries2019-01-146-14/+64
| | | |
| * | | Try implementing integer type inference (WIP)Marcus Klaas de Vries2019-01-148-46/+129
| | | |
| * | | Implement type inference for literals (WIP)Marcus Klaas de Vries2019-01-148-5/+166
| |/ /
* / / update cargo_metadataAleksey Kladov2019-01-142-3/+6
|/ /
* | switch to lsp-typesAleksey Kladov2019-01-1412-29/+29
| |
* | Remove duplicationJeremy Kolb2019-01-141-74/+23
| |
* | Add visibility to hoverJeremy Kolb2019-01-141-9/+41
|/
* target_selection_range is not nullable in the implementationAleksey Kladov2019-01-131-5/+10
|
* Merge #532bors[bot]2019-01-132-2/+21
|\ | | | | | | | | | | | | | | 532: fix go to parent module r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * fix go to parent moduleAleksey Kladov2019-01-132-2/+21
| |
* | Fix some random typosPascal Hertleif2019-01-133-10/+10
|/
* goto defenition works for type-inferred methodsAleksey Kladov2019-01-132-5/+71
|
* fix indent caclulationAleksey Kladov2019-01-133-11/+51
|
* Merge #520bors[bot]2019-01-136-3/+74
|\ | | | | | | | | | | | | | | | | | | | | | | 520: Imprement tuple inference r=flodiebold a=h-michael related #394 I'm sorry I'm late. I try implementing array inference next. Co-authored-by: Hirokazu Hata <[email protected]>
| * Fix tuple test caseHirokazu Hata2019-01-132-6/+35
| |
| * Implement tuple inferenceHirokazu Hata2019-01-132-1/+20
| |
| * Update TUPLE_EXPR grammarHirokazu Hata2019-01-132-2/+8
| |
| * Add infer tuple testHirokazu Hata2019-01-132-0/+17
| |
* | Tweak message shown for query fallbackPascal Hertleif2019-01-131-1/+5
|/ | | | Small tweak for #518
*-. Merge #517 #518bors[bot]2019-01-135-51/+114
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 517: gracefully handle cycles in crate graph r=matklad a=matklad 518: Add an explanatory message when we use the Query fallback r=matklad a=DJMcNab Fixes https://github.com/rust-analyzer/rust-analyzer/issues/269. There is no good way to explain it for go_to_def, so I've just fallen back on to_vec. Co-authored-by: Aleksey Kladov <[email protected]> Co-authored-by: DJMcNab <[email protected]>
| | * Add an explanatory message when we use the Query fallbackDJMcNab2019-01-132-10/+36
| | |
| * | gracefully handle cycles in crate graphAleksey Kladov2019-01-133-41/+78
| | | | | | | | | | | | | | | rust-lang/rust has absolutely weird setup with rustc-workspace-shim, which leads to real cycles.
* | | Merge #519bors[bot]2019-01-135-11/+46
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | 519: support ref-patterns r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | support ref-patternsAleksey Kladov2019-01-135-11/+46
| |/
* | Merge #513bors[bot]2019-01-133-35/+53
|\ \ | |/ |/| | | | | | | | | | | 513: Add bench runnable and code lens r=matklad a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * Add bench runnable and code lensJeremy Kolb2019-01-123-35/+53
| |
* | Fix typosJeremy Kolb2019-01-131-2/+2
|/
* Merge #505bors[bot]2019-01-1216-47/+398
|\ | | | | | | | | | | | | | | | | | | 505: Inherent methods r=matklad a=flodiebold This adds resolution, type checking and completion for inherent methods. The main open question here is the caching, I think. I'm not sure whether we should be caching method resolutions in a more fine grained way (currently we just build a hash map of types -> impl blocks, and iterate through all potential impl blocks when looking for a method). Co-authored-by: Florian Diebold <[email protected]>
| * args -> paramsFlorian Diebold2019-01-128-37/+37
| |
| * Small improvements from review commentsFlorian Diebold2019-01-123-20/+20
| |
| * Complete inherent methodsFlorian Diebold2019-01-123-4/+63
| |
| * Implement basic inherent method resolutionFlorian Diebold2019-01-1211-17/+309
| |
* | Merge #500bors[bot]2019-01-126-99/+154
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 500: Code lens support for running tests r=matklad a=kjeremy Supports running individual and mod tests. I feel like this kind of abuses the `Runnables` infrastructure but it works. Maybe later on down the line we should introduce a struct that is really just a tuple of binary, arguments, and environment and pass that back to the client instead. `run_single.ts` is just a paired down version of `runnables.ts` and there is duplication because I think run_single will probably change independent of runnables. Co-authored-by: Jeremy A. Kolb <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * | Move `CargoTargetSpec` and friends to cargo_target_spec moduleJeremy Kolb2019-01-123-90/+102
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 09:54:51 +0000