| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| | * | auto_import: use ra_fmt | Andrea Pretto | 2019-02-09 | 1 | -109/+29 | |
| | | | ||||||
| | * | auto_import: struct variants for ImportAction | Andrea Pretto | 2019-02-09 | 1 | -44/+107 | |
| | | | ||||||
| | * | auto_import: remove PathSegmentsMatch | Andrea Pretto | 2019-02-09 | 2 | -66/+37 | |
| | | | ||||||
| | * | auto_import: Removed Empty in favor of Partial(0) | Andrea Pretto | 2019-02-09 | 1 | -16/+10 | |
| | | | | | | | | | auto_import: Removed unecessary lifetimes | |||||
| | * | auto_import assist | Andrea Pretto | 2019-02-09 | 3 | -0/+784 | |
| | | | ||||||
| * | | 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. | |||||
| * | Merge #766 | bors[bot] | 2019-02-09 | 3 | -3/+3 | |
| |\ | | | | | | | | | | | | | | | | | | | 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 | 3 | -3/+3 | |
| | | | ||||||
| * | | 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 | 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 | |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |