I tried to do something like:
std::copy(std::make_move_iterator(s1.begin()), std::make_move_iterator(s1.end()),
std::make_move_iterator(s2.begin()));
And got this error:
error: using xvalue (rvalue reference) as lvalue
*__result = std::move(*__first);
Which seemed confusing to me. The same thing happens if you use std::move
. It appears that GCC internally uses a function called std::__copy_move_a
which moves rather than copies. Does it matter whether you use std::copy
or std::move
?
#include <string>
#include <iostream>
#include <algorithm>
#include <iterator>
#include <cstring>
struct Test
{
typedef std::string::value_type value_type;
std::string data;
Test()
{
}
Test(const char* data)
: data(data)
{
}
~Test()
{
}
Test(const Test& other)
: data(other.data)
{
std::cout << "Copy constructor.
";
}
Test& operator=(const Test& other)
{
data = other.data;
std::cout << "Copy assignment operator.
";
return *this;
}
Test(Test&& other)
: data(std::move(other.data))
{
std::cout << "Move constructor.
";
}
decltype(data.begin()) begin()
{
return data.begin();
}
decltype(data.end()) end()
{
return data.end();
}
void push_back( std::string::value_type ch )
{
data.push_back(ch);
}
};
int main()
{
Test s1("test");
Test s2("four");
std::copy(std::make_move_iterator(s1.begin()), std::make_move_iterator(s1.end()),
std::make_move_iterator(s2.begin()));
std::cout << s2.data;
}
See Question&Answers more detail:os