Lines Matching defs:move
70 AK_KnownsOnly = 0, // Warn only about known move-unsafe classes.
72 AK_All = 2, // Warn on any use-after-move.
96 // Not all of these are entirely move-safe, but they do provide *some*
97 // guarantees, and it means that somebody is using them after move
99 // TODO: We can still try to identify *unsafe* use after move,
116 // In non-aggressive mode, only warn on use-after-move of local variables
121 // move and their state-reset methods are also known, which allows us to
122 // predict precisely when use-after-move is invalid.
123 // Some STL objects are known to conform to additional contracts after move,
126 // In aggressive mode, warn on any use-after-move because the user has
127 // intentionally asked us to completely eliminate use-after-move
204 BugType BT{this, "Use-after-move", categories::CXXMoveSemantics};
234 namespace move {
239 } // namespace move
278 // We need only the last move of the reported object's region.
323 OS << " is left in a valid but unspecified state after move";
433 C.emitReport(std::move(R));
451 // Object can become moved from after a call to move assignment operator or
452 // move constructor .
527 // Don't report an error inside a move related operation.
554 // For the purposes of this checker, we classify move-safe STL types
658 // only for move or copy assignment's argument.