Why isn't the C 11 Move Constructor Called When Creating an Object from a Temporary Object?

C 11 Move Constructor Not Called, Default Constructor Preferred

In certain scenarios, the C 11 move constructor may not be invoked, favoring the default constructor instead. To understand why, let's examine an example.

Consider the following class:

<code class="cpp">class X {
public:
    explicit X (char* c) { cout <p>With this class, we can create objects as follows:</p>
<pre class="brush:php;toolbar:false"><code class="cpp">int main() {
    X x("test");
    cout <p>The expected output would be:</p>
<pre class="brush:php;toolbar:false">ctor
test
copy
test
ctor  <p>However, we observe that the move constructor is not called in the last line. Instead, the default constructor is used. To explain this, we need to understand <strong>copy elision</strong>.</p><p>Copy elision is an optimization technique allowed by the C  11 standard under certain conditions. It allows the compiler to construct a temporary object directly into the target object, avoiding the copy/move constructor and destructor overhead.</p><p>In this example, the X object created from the temporary "test" is elided into z. This means that no copy/move constructor is called, and instead, the object is constructed directly into z.</p><p>The compiler may perform copy elision when all of these conditions are met:</p>

• The object is a temporary object that has not been bound to a reference.
• The object is copied/moved to an object of the same cv-unqualified type.

In our case, these conditions are satisfied, and thus, copy elision occurs, causing the default constructor to be used instead of the move constructor. To explicitly call the move constructor, you can use std::move as seen in:

<code class="cpp">X z( std::move(X("test")) );</code>

The above is the detailed content of Why isn't the C 11 Move Constructor Called When Creating an Object from a Temporary Object?. For more information, please follow other related articles on the PHP Chinese website!