Why does calling std::move on a const object call the copy constructor when passed to another object?

后端 未结 2 1126
春和景丽
春和景丽 2020-12-15 04:35

Why does calling std::move on a const object call the copy constructor when passed to another object? Specifically, the code



        
2条回答
  •  粉色の甜心
    2020-12-15 05:15

    The type of the result of calling std::move with a T const argument is T const&&, which cannot bind to a T&& parameter. The next best match is your copy constructor, which is deleted, hence the error.

    Explicitly deleteing a function doesn't mean it is not available for overload resolution, but that if it is indeed the most viable candidate selected by overload resolution, then it's a compiler error.

    The result makes sense because a move construction is an operation that steals resources from the source object, thus mutating it, so you shouldn't be able to do that to a const object simply by calling std::move.

提交回复
热议问题