[cfe-dev] deprecating copy construction and assignment
hhinnant at apple.com
Mon Apr 2 11:50:44 PDT 2012
On Apr 2, 2012, at 2:43 PM, Richard Smith wrote:
> On Thu, Mar 29, 2012 at 2:09 PM, Richard Smith <richard at metafoo.co.uk> wrote:
> On Thu, Mar 29, 2012 at 12:06 PM, Howard Hinnant <hhinnant at apple.com> wrote:
> I just became aware of cwg 1402 which is in ready status:
> This change will no longer make A's move members deleted. Instead A will get move members that copy the data member.
> This is a very good change as the current rules are extremely error prone. The library section of the standard itself was bitten by these rules in the move constructor of both tuple and pair (which are explicitly defaulted).
> As this issue is both non-controversial, and already in ready status, I think it would be a good idea to go ahead and implement it. That will likely be easier than designing warnings for the implicit deletion of explicitly defaulted move members.
> I agree. I happen to be currently working on the implicit deletion of special member functions anyway, so I'll make this change.
> This is now implemented in r153883.
More information about the cfe-dev