«

On Saturday, April 7, 2012 5:59:28 PM UTC-5, woodb...@gmail.com wrote:
> On Saturday, April 7, 2012 12:34:01 PM UTC-5, Howard Hinnant wrote:
> >
> > I agree too. However it is good to be aware of the cases that do
> > break, so you can learn to recognize them, and learn how to fix them.
> >
>
> Right.
>
> > The most convincing case I've seen to date is this one:
> >
>
> Thanks for the detailed explanation.
>
>
> > Image(Image&& img)
> > : m_data(std::move(img.m_data)),
>
> I recall something Anthony Williams wrote about the
> members of an rvalue reference being rvalue references
> and not needing to use std::move there. Perhaps you
> use it as a reminder of what is happening and not
> because it's really needed?

I read the thread you linked to in the moderated group
now and the std::move is needed. It's been a while since
I read what Anthony wrote so don't know if I'm remembering
things wrong or he was mistaken.

On 8 Apr., 00:59, woodbria... wrote:
> On Saturday, April 7, 2012 12:34:01 PM UTC-5, Howard Hinnant wrote:
>
> > The most convincing case I've seen to date is this one:
>
> Thanks for the detailed explanation.
>
> > * * Image(Image&& img)
> > * * * * : m_data(std::move(img.m_data)),
>
> I recall something Anthony Williams wrote about the
> members of an rvalue reference being rvalue references
> and not needing to use std::move there. *Perhaps you
> use it as a reminder of what is happening and not
> because it's really needed?

References have no members. And `img` is an lvalue expression. So an
explicit std::move is required to select the move constructor. But
you can also write

std::move(img).m_data

because member access on an rvalue expression yields an rvalue
expression.

Cheers!
SG