# Add Iterator::into\_vec()

**URL:** https://internals.rust-lang.org/t/add-iterator-into-vec/4845
**Category:** libs
**Created:** [February 24, 2017, 2:16pm UTC](https://internals.rust-lang.org/t/add-iterator-into-vec/4845 "2017-02-24T14:16:00Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![leonardo](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/leonardo/32/1344_2.png) [@leonardo](https://internals.rust-lang.org/u/leonardo)
#### Post date: [February 24, 2017, 6:01pm UTC](https://internals.rust-lang.org/t/add-iterator-into-vec/4845/5 "2017-02-24T18:01:07Z")

</div>

I've written some comments in the closed thread.

This feature goes according to:

> [@\[Roadmap 2017\] Productivity: learning curve and expressiveness](https://internals.rust-lang.org/t/roadmap-2017-productivity-learning-curve-and-expressiveness/4097/109):
>
> Compared to all the times I had to code review “you should be moving that shared\_ptr\<\> in C++”, I really like Rust’s existing choices here. Copy when it’s trivial enough to not care, move by default so the right thing usually happens without thinking, but also really easy to .clone() when you have to. (I needed to, essentially, .clone() a SqlParameter in C# the other day, and it was miserable. C#'s IClonable totally doesn’t work, and canonical C# doesn’t reliably even have a “copy constructor…

---

_[View the full topic](https://internals.rust-lang.org/t/add-iterator-into-vec/4845)._