c – 临时对象的子对象是否保证在返回时被移动?

#include <string>
#include <vector>

using namespace std;

auto f()
{
    vector<string> coll{ "hello" };

    //
    // Must I use move(coll[0]) ?
    //
    return coll[0]; 
}

int main()
{
    auto s = f();
    DoSomething(s);
}

我知道:如果我只是返回coll,那么coll保证在返回时被移动.

不过,我不确定:coll [0]是否也保证在返回时被移动?

更新:

#include <iostream>

struct A
{
    A() { std::cout << "constructed\n"; }
    A(const A&) { std::cout << "copy-constructed\n"; }
    A(A&&) { std::cout << "move-constructed\n"; }
    ~A() { std::cout << "destructed\n"; }
};

struct B
{
    A a;
};

A f()
{
    B b;
    return b.a;
}

int main()
{
    f();
}

gcc 6.2和clang 3.8输出相同:

constructed

copy-constructed

destructed

destructed

解决方法

“隐性移动”规则的最干净的表述是目前工作文件[class.copy.elision]/3

In the following copy-initialization contexts,a move operation might
be used instead of a copy operation:

  • If the expression in a return statement ([stmt.return]) is a (possibly parenthesized) id-expression that names an object with
    automatic storage duration declared in the body or
    parameter-declaration-clause of the innermost enclosing function or lambda-expression,or

  • […]

overload resolution to select the constructor for the copy is first
performed as if the object were designated by an rvalue. If the first
overload resolution fails or was not performed,or if the type of the
first parameter of the selected constructor is not an rvalue reference
to the object’s type (possibly cv-qualified),overload resolution is
performed again,considering the object as an lvalue.

b.a和coll [0]都不是id表达式.所以没有隐含的动作.如果你想要一个举动,你必须明确地做.

相关文章

本程序的编译和运行环境如下(如果有运行方面的问题欢迎在评...
水了一学期的院选修,万万没想到期末考试还有比较硬核的编程...
补充一下,先前文章末尾给出的下载链接的完整代码含有部分C&...
思路如标题所说采用模N取余法,难点是这个除法过程如何实现。...
本篇博客有更新!!!更新后效果图如下: 文章末尾的完整代码...
刚开始学习模块化程序设计时,估计大家都被形参和实参搞迷糊...