Tracking issue for collection append methods

[alexcrichton]

This is a tracking issue for the unstable append feature in the standard library. It's somewhat unclear if these methods need to be stabilized, but it's also fairly clear that they're not going to change from their current form. They will likely go into FCP soon.

cc @Gankro.

[Gankro]

foo.append(bar) is semantically foo.extend(bar.drain(..)). Pretty specific, but ripe for optimization. In particular it was motivated by LinkedList which can just mangle some pointers instead of actually moving anything. It's also stable on LinkedList.

In principle, specialization "solves" this function in a much more flexible way.

[alexcrichton]

This feature is now entering its final comment period for stabilization.

[alexcrichton]

@hartsantler's thoughts:

Coming from Python, as many others probably are, i find the method name append to be misleading.
From the rust docs:
http://doc.rust-lang.org/std/vec/struct.Vec.html#method.append

Moves all the elements of other into Self, leaving other empty.

This is similar to the extend method in Python, but still a little different because it moves the elements into self. I think it makes much sense to call the method something like: merge or move_from