Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix introduce var duplicating newlines | Ville Penttinen | 2019-02-09 | 1 | -1/+80 |
| | | | | | | | | | | | | | This fixes #713. If the block before the statement we want to use introduce var on, had empty lines these empty lines would also be added between the let-statement and the current line where the new variable is used. This fixes that by trimming excess newlines from the start of the indent chunk and simply adding a single newline (when the chunk had newlines) between the let-statement and the current statement. If there were no newlines this matches the previous behaviour. | ||||
* | Clean up a bit | Florian Diebold | 2019-02-09 | 2 | -3/+1 |
| | |||||
* | Remove Vfs from project model | Florian Diebold | 2019-02-09 | 3 | -8/+8 |
| | |||||
* | Remove SmolStr from project model | Florian Diebold | 2019-02-09 | 4 | -18/+7 |
| | |||||
* | Move crate graph generation to ra_project_model | Florian Diebold | 2019-02-09 | 4 | -83/+113 |
| | |||||
* | Extract project model to separate crate | Florian Diebold | 2019-02-09 | 7 | -52/+94 |
| | |||||
* | Merge #766 | bors[bot] | 2019-02-09 | 9 | -9/+23 |
|\ | | | | | | | | | | | | | | | | | | | 766: Formatting code into ra_fmt r=matklad a=eulerdisk As discussed https://github.com/rust-analyzer/rust-analyzer/pull/762#discussion_r254905885 I did only move the code without other improvements. Co-authored-by: Andrea Pretto <[email protected]> | ||||
| * | Refactor formatting code out of ra_ida_api_light into ra_fmt. | Andrea Pretto | 2019-02-08 | 9 | -9/+23 |
| | | |||||
* | | Improve sorting delegate | robojumper | 2019-02-09 | 1 | -7/+5 |
| | | |||||
* | | Remove unused import | robojumper | 2019-02-08 | 1 | -2/+2 |
| | | |||||
* | | Add tests for action target ranges | robojumper | 2019-02-08 | 10 | -16/+210 |
| | | |||||
* | | Add some assist ranges | robojumper | 2019-02-08 | 5 | -10/+58 |
|/ | |||||
* | reformat the world | Aleksey Kladov | 2019-02-08 | 129 | -2510/+728 |
| | |||||
* | diagnostics is now a function | Aleksey Kladov | 2019-02-08 | 2 | -64/+62 |
| | |||||
* | move diagnostics to a separate file | Aleksey Kladov | 2019-02-08 | 2 | -27/+22 |
| | |||||
* | move index_resolve to symbol index | Aleksey Kladov | 2019-02-08 | 4 | -14/+11 |
| | |||||
* | move find_references to references | Aleksey Kladov | 2019-02-08 | 3 | -67/+55 |
| | |||||
* | avoid 'ignored' in test output | Aleksey Kladov | 2019-02-08 | 1 | -2/+2 |
| | |||||
* | rename rename to references | Aleksey Kladov | 2019-02-08 | 2 | -2/+2 |
| | |||||
* | move crate for | Aleksey Kladov | 2019-02-08 | 3 | -16/+16 |
| | |||||
* | move changes to a separate file | Aleksey Kladov | 2019-02-08 | 4 | -254/+263 |
| | |||||
* | Remove unnecessary dbg! calls | Ville Penttinen | 2019-02-07 | 1 | -3/+2 |
| | |||||
* | Add new assist to remove dbg!() calls | Ville Penttinen | 2019-02-07 | 2 | -0/+126 |
| | | | | | | | | | | | | | | | | | This fixes #758. Currently we try to maintain the cursor position relative to the statement under cursor, if the cursor is inside the dbg! macro call. Meaning: let foo = dbg!(some.complex<|>().expression()); Should turn into: let foo = some.complex<|>().expression(); With the cursor staying in place. | ||||
* | Some clippy cleanups | kjeremy | 2019-02-06 | 15 | -55/+49 |
| | |||||
* | assists: compute edit | kjeremy | 2019-02-06 | 1 | -1/+1 |
| | |||||
* | move assists to a separate crate | Aleksey Kladov | 2019-02-06 | 25 | -580/+568 |
| | |||||
* | Remove stray dbg! | Jeremy Kolb | 2019-02-06 | 1 | -1/+1 |
| | |||||
* | Fill deprecation for LSP | kjeremy | 2019-02-05 | 6 | -23/+86 |
| | |||||
* | Rename assits to assists | Jeremy Kolb | 2019-02-05 | 6 | -5/+5 |
| | |||||
* | Merge #740 | bors[bot] | 2019-02-05 | 6 | -7/+7 |
|\ | | | | | | | | | | | | | | | | | 740: Update dependencies r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]> | ||||
| * | Remove unused imports | Jeremy Kolb | 2019-02-05 | 2 | -2/+2 |
| | | |||||
| * | Bump insta and proptest to latest | kjeremy | 2019-02-04 | 4 | -5/+5 |
| | | |||||
* | | Merge #742 | bors[bot] | 2019-02-05 | 14 | -48/+190 |
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 742: Extern crate r=matklad a=flodiebold This implements `extern crate` declarations by lowering them to (absolute) imports, and adds support for absolute paths. It also extracts the extern prelude from the per-module item map, and handles the special case of extern crates in the crate root adding to the extern prelude. This means we finally resolve `Arc`, so it fixes #523 :smile: Co-authored-by: Florian Diebold <[email protected]> | ||||
| * | | Fix ReachedFixedPoint value for unresolved external prelude items | Florian Diebold | 2019-02-04 | 1 | -1/+1 |
| | | | |||||
| * | | Complete extern prelude (again) | Florian Diebold | 2019-02-04 | 4 | -2/+41 |
| | | | |||||
| * | | Make it possible to have multiple crate in a mock analysis fixture | Florian Diebold | 2019-02-04 | 1 | -2/+10 |
| | | | |||||
| * | | Add alloc to std deps | Florian Diebold | 2019-02-04 | 1 | -0/+1 |
| | | | |||||
| * | | Make extern crates in the root module add to the extern prelude | Florian Diebold | 2019-02-04 | 4 | -39/+68 |
| | | | | | | | | | | | | To accomplish this, separate the extern prelude from the per-module item maps. | ||||
| * | | Lower extern crates to imports | Florian Diebold | 2019-02-04 | 1 | -3/+16 |
| | | | | | | | | | | | | This is probably not completely correct, but it kind of works. | ||||
| * | | Add test for extern crate renames | Florian Diebold | 2019-02-04 | 1 | -0/+42 |
| | | | |||||
| * | | Add AST for extern crate | Florian Diebold | 2019-02-04 | 5 | -6/+16 |
| | | | | | | | | | | | | Also change it to parse the crate name as a NAME_REF, not a NAME. | ||||
* | | | Merge #743 | bors[bot] | 2019-02-05 | 1 | -12/+13 |
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 743: Move comment r=matklad a=kjeremy As pointed out in https://github.com/rust-analyzer/rust-analyzer/pull/738/files#r253651450 Co-authored-by: kjeremy <[email protected]> | ||||
| * | | | Move comment | kjeremy | 2019-02-04 | 1 | -12/+13 |
| |/ / | |||||
* | | | Merge #744 | bors[bot] | 2019-02-05 | 2 | -2/+30 |
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | 744: mbe: Ensure repetition separator matches r=matklad a=jrmuizel Co-authored-by: Jeff Muizelaar <[email protected]> | ||||
| * | | mbe: Ensure repetition separator matches | Jeff Muizelaar | 2019-02-05 | 2 | -2/+30 |
| | | | |||||
* | | | Merge #741 | bors[bot] | 2019-02-04 | 2 | -3/+13 |
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 741: Test more Self inference r=flodiebold a=kjeremy These cases didn't look covered. Co-authored-by: kjeremy <[email protected]> | ||||
| * | | | Test more Self inference | kjeremy | 2019-02-04 | 2 | -3/+13 |
| | |/ | |/| | |||||
* / | | Future proof by explicitly matching against None | kjeremy | 2019-02-04 | 1 | -1/+1 |
|/ / | |||||
* | | Add comment | kjeremy | 2019-02-04 | 1 | -0/+4 |
| | | |||||
* | | Implement lens for impls and support resolving lenses. | Jeremy Kolb | 2019-02-04 | 3 | -3/+85 |
|/ |