Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Better cursor placement when adding impl members | Aleksey Kladov | 2020-05-20 | 1 | -38/+46 |
| | |||||
* | Use snippets in add_missing_members | Aleksey Kladov | 2020-05-20 | 1 | -27/+35 |
| | |||||
* | Correctly fill default type parameters | Fedor Sakharov | 2020-05-13 | 1 | -0/+50 |
| | |||||
* | More fluent indent API | Aleksey Kladov | 2020-05-09 | 1 | -3/+2 |
| | |||||
* | Refactor assists API to be more convenient for adding new assists | Aleksey Kladov | 2020-05-07 | 1 | -15/+17 |
| | | | | It now duplicates completion API in its shape. | ||||
* | Move target to AssistLabel | Aleksey Kladov | 2020-05-06 | 1 | -7/+7 |
| | | | | | Target is used for assists sorting, so we need it before we compute the action. | ||||
* | Merge assits::test_helpers and tests | Aleksey Kladov | 2020-05-06 | 1 | -1/+1 |
| | |||||
* | Rename ImplItem to AssocItem | Edwin Cheng | 2020-05-05 | 1 | -13/+13 |
| | |||||
* | Add missing members generates indented blocks | Aleksey Kladov | 2020-05-02 | 1 | -78/+116 |
| | |||||
* | Change missing impl assist to use todo!() instead of unimplemented() | Chris Hopman | 2020-04-10 | 1 | -17/+17 |
| | | | | | | | | | | | | todo!() "Indicates unfinished code" (https://doc.rust-lang.org/std/macro.todo.html) Rust documentation provides further clarification: > The difference between unimplemented! and todo! is that while todo! > conveys an intent of implementing the functionality later and the > message is "not yet implemented", unimplemented! makes no such claims. todo!() seems more appropriate for assists that insert missing impls. | ||||
* | Align naming | Aleksey Kladov | 2020-03-24 | 1 | -1/+1 |
| | |||||
* | Simplify | Aleksey Kladov | 2020-03-13 | 1 | -2/+2 |
| | |||||
* | Rename ast::ImplBlock -> ast::ImplDef | Aleksey Kladov | 2020-02-29 | 1 | -3/+3 |
| | |||||
* | Refactor primary IDE API | Aleksey Kladov | 2020-02-26 | 1 | -18/+11 |
| | | | | | | | | | | This introduces the new type -- Semantics. Semantics maps SyntaxNodes to various semantic info, such as type, name resolution or macro expansions. To do so, Semantics maintains a HashMap which maps every node it saw to the file from which the node originated. This is enough to get all the necessary hir bits just from syntax. | ||||
* | Formatted changes. | Kevin DeLorey | 2020-02-11 | 1 | -2/+2 |
| | |||||
* | Fixed warning generated after refactoring. | Kevin DeLorey | 2020-02-11 | 1 | -1/+1 |
| | |||||
* | Updated the `add_missing_impl_members` to use the shared utility. | Kevin DeLorey | 2020-02-11 | 1 | -33/+14 |
| | |||||
* | Name assist handlers | Aleksey Kladov | 2020-02-07 | 1 | -0/+608 |