| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Implement "Extract type alias" assist | Jonas Schievink | 2021-03-26 | 1 | -0/+19 |
| | | |||||
| * | 7709: Updated the implementation. | Chetan Khilosiya | 2021-03-15 | 1 | -0/+4 |
| | | | | | | The get function from impl method is updated. and now same method used to get len and is_empty function. | ||||
| * | 7709: Added the assist to generate is_empty function | Chetan Khilosiya | 2021-03-15 | 1 | -0/+25 |
| | | | | | | the assist will be shown when the len function is implemented. is_empty internally uses len function. | ||||
| * | Fix convert_iter_for_each_to_for doctest | Lukas Wirth | 2021-03-12 | 1 | -4/+11 |
| | | |||||
| * | fix: generated test fixture | Luiz Carlos Mourão Paes de Carvalho | 2021-03-12 | 1 | -0/+23 |
| | | |||||
| * | 7708: Fixed many documentaion example issues. | Chetan Khilosiya | 2021-03-06 | 1 | -0/+31 |
| | | |||||
| * | Use consistent naming for assist | Aleksey Kladov | 2021-02-28 | 1 | -23/+23 |
| | | |||||
| * | generate try_into instead of into | Domantas Jadenkus | 2021-02-27 | 1 | -29/+29 |
| | | |||||
| * | add generate_enum_as_method assist | Domantas Jadenkus | 2021-02-27 | 1 | -0/+29 |
| | | |||||
| * | add generate_enum_into_method assist | Domantas Jadenkus | 2021-02-27 | 1 | -0/+29 |
| | | |||||
| * | rename existing assist to generate_enum_is_method | Domantas Jadenkus | 2021-02-27 | 1 | -2/+2 |
| | | |||||
| * | Merge #7741 | bors[bot] | 2021-02-24 | 1 | -0/+23 |
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7741: Add convert_for_to_iter_for_each assist r=mattyhall a=mattyhall Implements one direction of #7681 I wonder if this tries to guess too much at the right thing here. A common pattern is: ```rust let col = vec![1, 2, 3]; for v in &mut col { *v *= 2; } // equivalent to: col.iter_mut().for_each(|v| *v *= 2); ``` I've tried to detect this case by checking if the expression after the `in` is a (mutable) reference and if not inserting iter()/iter_mut(). This is just a convention used in the stdlib however, so could sometimes be wrong. I'd be happy to make an improvement for this, but not sure what would be best. A few options spring to mind: 1. Only allow this for types that are known to have iter/iter_mut (ie stdlib types) 2. Try to check if iter/iter_mut exists and they return the right iterator type 3. Don't try to do this and just add `.into_iter()` to whatever is after `in` Co-authored-by: Matt Hall <[email protected]> | ||||
| | * | Add convert_for_to_iter_for_each assist | Matt Hall | 2021-02-23 | 1 | -0/+23 |
| | | | |||||
| * | | De Morgan's Law assist now correctly inverts <, <=, >, >=. | lbrande | 2021-02-24 | 1 | -2/+2 |
| | | | |||||
| * | | De Morgan's Law assist now correctly parenthesizes binary expressions. | lbrande | 2021-02-24 | 1 | -2/+2 |
| |/ | |||||
| * | 7526: Rename crate assists to ide_assists. | Chetan Khilosiya | 2021-02-22 | 1 | -0/+1329 |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |