>How would this even help with the confusion you have?

>This would still call the copy constructor, so >if you're logging in your copy constructor and >copy assignment operator, you'll still see that >some elements in the vector were modified >by copy assignment, and new elements were >initialized by copy construction. So you'll still >see "A::A(const A&)" for your example above!

[ One suggestion is to add 2 new special functions ]...i guess its clear the context is about the proposal not the " confusion"

>So this doesn't even help with the one thing >that you think it would be useful for.

>So combined with being completely >unimplementable (because in the general >case the compiler can't tell whether >assignment is to an existing object or to raw >memory), this is just a terrible idea that >doesn't even work.