Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | | 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 | 9 | -96/+27 | |
| | ||||||
* | 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 | 1 | -3/+3 | |
| | ||||||
* | assists: compute edit | kjeremy | 2019-02-06 | 1 | -1/+1 | |
| | ||||||
* | move assists to a separate crate | Aleksey Kladov | 2019-02-06 | 11 | -0/+1406 | |