aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_assists/src/lib.rs
Commit message (Collapse)AuthorAgeFilesLines
* Merge #989bors[bot]2019-03-181-0/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 989: Implement naive version of fill_struct_fields assist r=matklad a=yanchith Fixes #964 This implements the `fill_struct_fields` assist. Currently only works for named struct fields, but not for tuple structs, because we seem to be missing a `TupleStructLit` (akin to `StructLit`, but for tuple structs). I am happy to implement `TupleStructLit` parsing given some guidance (provided it's really missing) and make the assist work for tuple structs as well. Could do so either in this PR, or another one 🙂 Sorry if I missed something important, this is my first PR for Rust Analyzer. Btw is there any way to run the assists in emacs? UPDATE: I just realized that parsing `TupleStructLit` would be quite difficult as it it really similar, if not identical to a function call... Co-authored-by: yanchith <[email protected]>
| * Implement naive version of fill_struct_fields assistyanchith2019-03-171-0/+2
| |
* | Add 'add_missing_impl_members' assist stubIgor Matuszewski2019-03-161-0/+2
|/
* add marks to assistsAleksey Kladov2019-02-241-0/+1
|
* dont show introduce variable everywhereAleksey Kladov2019-02-241-5/+15
|
* Assign IDs to assistsAleksey Kladov2019-02-241-0/+6
|
* Move `non_trivia_sibling` to `ra_syntax::algo`Ville Penttinen2019-02-211-5/+1
|
* Fix some typosPascal Hertleif2019-02-121-1/+1
|
* ra_assists: assist "providers" can produce multiple assistsAndrea Pretto2019-02-111-16/+59
|
* auto_import assistAndrea Pretto2019-02-091-0/+3
|
* Improve sorting delegaterobojumper2019-02-091-7/+5
|
* Remove unused importrobojumper2019-02-081-2/+2
|
* Add tests for action target rangesrobojumper2019-02-081-3/+63
|
* Add some assist rangesrobojumper2019-02-081-3/+37
|
* reformat the worldAleksey Kladov2019-02-081-11/+5
|
* Add new assist to remove dbg!() callsVille Penttinen2019-02-071-0/+2
| | | | | | | | | | | | | | | | | 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.
* assists: compute editkjeremy2019-02-061-1/+1
|
* move assists to a separate crateAleksey Kladov2019-02-061-0/+170