id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
11786	Shouldn't boost::container::vector handle self-move-assignment?	fredrik.astrom89@…	Ion Gaztañaga	"Right now boost::container::vector disallows self-move-assignment. Looking at this seems to have been done by mistake. 
The code in question(taken from the function priv_move_assign in boost/container/vector.hpp) says:

{{{
//for move constructor, no aliasing (&x != this) is assummed.
BOOST_ASSERT(this != &x); 
}}}
(where x is the parameter)

As this isn't a move constructor I can only assume this is a mistake.
If it isn't a mistake, just a bad comment, then I'd still argue that this should be changed. Mostly because VS2015 implementation of std::stable_partition assumes that self-move-assignment works..."	Bugs	closed	To Be Determined	container	Boost 1.59.0	Problem	fixed