# \`Vec::append\` but by value

**URL:** <https://internals.rust-lang.org/t/vec-append-but-by-value/21029>\
**Category:** language design\
**Created:** [June 14, 2024, 3:18am UTC](https://internals.rust-lang.org/t/vec-append-but-by-value/21029 "2024-06-14T03:18:16Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![Ratatouille](https://avatars.discourse-cdn.com/v4/letter/r/57b2e6/32.png) [@Ratatouille](https://internals.rust-lang.org/u/Ratatouille)\
**Post date:** [June 17, 2024, 8:26am UTC](https://internals.rust-lang.org/t/vec-append-but-by-value/21029/16 "2024-06-17T08:26:47Z")

</div>

> [@Weird syntax idea(s) for UMCS](https://internals.rust-lang.org/t/weird-syntax-idea-s-for-umcs/19200/13):
>
> As a user of rust (as opposed to a developer on rust itself), this would be very nice. One use case where I ran into this was when using itertools. Specially the intersperse method from itertools. There is an unstable intersperse method in the std iterator trait. If I don't use the fully qualified name for the itertools intersperse I got a warning (forget if it was clippy or rustc). If I do use the fully qualified name, I can't use the chain of method calls (i.e. a.iter().something(...).intersp…

---

_[View the full topic](https://internals.rust-lang.org/t/vec-append-but-by-value/21029)._