From Josuttis 's The C++ Standard Library
You don’t have to and should not move() return values. According to the language rules, the standard specifies that for the following code
X foo ()
{
X x;
...
return x;
}
the following behavior is guaranteed:
? If X has an accessible copy or move constructor, the compiler may
choose to elide the copy. This is the so-called (named) return value
optimization ((N)RVO), which was specified even before C++11 and is
supported by most compilers.
? Otherwise, if X has a move constructor, x is moved.
? Otherwise, if X has a copy constructor, x is copied.
? Otherwise, a compile-time error is emitted.
From §25.2.4 (for_each)
Requires:Function shall meet the requirements of MoveConstructible
(Table 20). [Note:Function need not meet the requirements of
CopyConstructible (Table 21).—end note]
With std::move(f)
you can be guaranteed of being able to read the mutated state externally.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…