Question

Suppose we have this class:

class X {
public:
    explicit X (char* c) { cout<<"ctor"<<endl; init(c); };
    X (X& lv)  { cout<<"copy"<<endl;  init(lv.c_); };
    X (X&& rv) { cout<<"move"<<endl;  c_ = rv.c_; rv.c_ = nullptr; };

    const char* c() { return c_; };

private:
    void init(char *c) { c_ = new char[strlen(c)+1]; strcpy(c_, c); };
    char* c_;

};

and this sample usage:

X x("test");
cout << x.c() << endl;
X y(x);
cout << y.c() << endl;
X z( X("test") );
cout << z.c() << endl;

The output is:

ctor
test
copy
test
ctor   <-- why not move?
test

I am using VS2010 with default settings. I’d expect the last object (z) to be move-constructed, but it’s not! If I use X z( move(X("test")) ); then the last lines of the output are ctor move test, as I’d expect. Is it a case of (N)RVO?

Q: Should the move-ctor be called according to the standard? If so, why isn’t it called?

Answer 1

What you are seeing is copy elision, which allows the compiler to directly construct a temporary into a target it is to be copied/moved into and thus elide a copy (or move) constructor/destructor pair. The situations in which the compiler is allowed to apply copy elision are specified in §12.8.32 of the C++11 standard:

When certain criteria are met, an implementation is allowed to omit
the copy/move construction of a class object, even if the copy/move
constructor and/or destructor for the object have side effects. In such
cases, the implementation treats the source and target of the omitted
copy/move operation as simply two different ways of referring to the
same object, and the destruction of that object occurs at the later of
the times when the two objects would have been destroyed without the
optimization. This elision of copy/move
operations, called copy elision, is permitted in the following
circumstances (which maybe combined to eliminate multiple copies):

• in a return statement in a function with a class return type, when the expression is the name of a non-volatile automatic object with
  the same cv-unqualified type as the function return type, the
  copy/move operation can be omitted by constructing the automatic
  object directly into the function’s return value
• in a throw-expression, when the operand is the name of a non-volatile automatic object whose scope does not extend beyond
  the end of the innermost enclosing try-block (if there is one), the
  copy/move operation from the operand to the exception object (15.1)
  can be omitted by constructing the automatic object directly into
  the exception object
• when a temporary class object that has not been bound to a reference (12.2) would be copied/moved to a class object with he
  same cv-unqualified type, the copy/move operation can be omitted by
  constructing the temporary object directly into the target of the
  omitted copy/move
• when the exception-declaration of an exception handler (Clause 15) declares an object of the same type (except for cv-qualification) as
  the exception object (15.1), the copy/move operation can be omitted
  bytreatingthe exception-declaration as an alias for the exception
  object if the meaning of the program will be unchanged except for the
  execution of constructors and destructors for the object declared by
  the exception-declaration.