suggest .into_iter() when trying to collect Vec<T> into Vec<T>

[matthiaskrgr]

Given the following code:

fn main() {
    let v: Vec<String> = Vec::new();
    let v2: Vec<String> = v.iter().filter(|s| s.len() == 2).collect();
}

The current output is:

error[E0277]: a value of type `Vec<String>` cannot be built from an iterator over elements of type `&String`
 --> src/main.rs:3:61
  |
3 |     let v2: Vec<String> = v.iter().filter(|s| s.len() == 2).collect();
  |                                                             ^^^^^^^ value of type `Vec<String>` cannot be built from `std::iter::Iterator<Item=&String>`
  |
  = help: the trait `FromIterator<&String>` is not implemented for `Vec<String>`

error: aborting due to previous error

Instead of somehow trying to call .clone() on the Strings, if v is not used anywhere else, one can easily fix this problem by calling v2 .. = v.into_iter() instead of v2 .. = v.iter().
Does it make sense for rustc to suggest that?

[MoreTacos]

I totally support this. A few months ago I tried to use some functional programming paradigms in Rust I got very confused with ownership when using iterators into maps.

If I would have known about into_iter my life would have been a lot easier.