Cur*_*ous 16 c++ rvalue copy-elision c++17 structured-bindings
强制复制省略是否适用于通过结构化绑定进行分解?以下哪种情况适用于?
// one
auto [one, two] = std::array<SomeClass>{SomeClass{1}, SomeClass{2}};
// two
auto [one, two] = std::make_tuple(SomeClass{1}, SomeClass{2});
// three
struct Something { SomeClass one, two; };
auto [one, two] = Something{};
Run Code Online (Sandbox Code Playgroud)
我怀疑只有第三种情况允许复制省略,因为前两个会被"分解"通过std::get<>并std::tuple_size<>和std::get<>当参数是右值返回xvalues
标准的引用也很好!
Bar*_*rry 16
强制复制省略是否适用于通过结构化绑定进行分解?以下哪种情况适用于?
是的,所有这些.结构化绑定的目的是为您提供对要绑定的类型的析构元素的命名引用.这个:
auto [one, two] = expr;
Run Code Online (Sandbox Code Playgroud)
只是语法糖:
auto __tmp = expr;
some_type<0,E>& a = some_getter<0>(__tmp);
some_type<1,E>& b = some_getter<1>(__tmp);
Run Code Online (Sandbox Code Playgroud)
凡some_type与some_getter依赖于我们解构的那种类型(数组,元组等,或用类型所有公共非静态数据成员).
强制性复制省略适用于该auto __tmp = expr行,其他行均不涉及复制.
关于评论中的一个例子存在一些混淆,所以让我详细说明发生的事情:
auto [one, two] = std::make_tuple(Something{}, Something{});
Run Code Online (Sandbox Code Playgroud)
这扩展到:
auto __tmp = std::make_tuple(Something{}, Something{}); // note that it is from
// std::make_tuple() itself that we get the two default constructor calls as well
// as the two copies.
using __E = std::remove_reference_t<decltype(__tmp)>; // std::tuple<Something, Something>
Run Code Online (Sandbox Code Playgroud)
然后,因为__E它不是数组类型而是类似元组,我们通过非限定调用get__E引入变量来查找相关的命名空间.初始化程序将是一个xvalue,类型将是rvalue引用:
std::tuple_element_t<0, __E>&& one = get<0>(std::move(__tmp));
std::tuple_element_t<1, __E>&& two = get<1>(std::move(__tmp));
Run Code Online (Sandbox Code Playgroud)
需要注意的是,虽然one和two都是右值引用到__tmp,decltype(one)并且decltype(two)将两者的产量Something,而不是Something&&.