Move operations and valid remaining state

The idea

std::move casts an expression so overload resolution can select a move operation. It does not itself transfer resources, erase a value, or run a destructor. The receiving constructor or assignment performs whatever move behavior its type defines. Some types may copy instead, and an optimizing implementation need not have the internal behavior you imagined.

A moved-from standard-library object remains valid but its value is generally unspecified unless the type documents a stronger guarantee. Destroying it or assigning a new value is safe; asserting that a moved-from string must be empty is not portable. Keep the destination’s required value separate from assumptions about the source. Prefer ordinary value and RAII types so their move rules manage resources without hand-written ownership transfers.

#include <iostream>
#include <string>
#include <utility>
int main() {
  std::string source = "report";
  std::string destination = std::move(source);
  source = "new";
  std::cout << destination << ' ' << source;
}

report new

The destination receives the original text; assigning a new value to the valid moved-from source is supported.