How to enforce move semantics when a vector grows?

by

You need to inform C++ (specifically std::vector) that your move constructor and destructor does not throw, using noexcept. Then the move constructor will be called when the vector grows.

This is how to declare and implement a move constuctor that is respected by std::vector:

A(A && rhs) noexcept { 
  std::cout << "i am the move constr" <<std::endl;
  ... some code doing the move ...  
  m_value=std::move(rhs.m_value) ; // etc...
}

If the constructor is not noexcept, std::vector can’t use it, since then it can’t ensure the exception guarantees demanded by the standard.

For more about what’s said in the standard, read
C++ Move semantics and Exceptions

Credit to Bo who hinted that it may have to do with exceptions. Also consider Kerrek SB’s advice and use emplace_back when possible. It can be faster (but often is not), it can be clearer and more compact, but there are also some pitfalls (especially with non-explicit constructors).

Edit, often the default is what you want: move everything that can be moved, copy the rest. To explicitly ask for that, write

A(A && rhs) = default;

Doing that, you will get noexcept when possible: Is the default Move constructor defined as noexcept?

Note that early versions of Visual Studio 2015 and older did not support that, even though it supports move semantics.

More Related Contents:

  1. Is a moved-from vector always empty?
  2. Initializer-list-constructing a vector of noncopyable (but movable) objects
  3. How can I resize a 2D vector of objects given the width and height?
  4. Invalid operands to binary expression while implementing vector [closed]
  5. What is move semantics?
  6. What is std::move(), and when should it be used?
  7. What can I do with a moved-from object?
  8. Can I list-initialize a vector of move-only type?
  9. Does C++11 allow vector?
  10. Why no default move-assignment/move-constructor?
  11. Is this behavior of vector::resize(size_type n) under C++11 and Boost.Container correct?
  12. What constitutes a valid state for a “moved from” object in C++11?
  13. What are the rules for automatic generation of move operations?
  14. C++11 move constructor not called, default constructor preferred
  15. Is the pass-by-value-and-then-move construct a bad idiom?
  16. How does std::move() transfer values into RValues?
  17. std::vector, default construction, C++11 and breaking changes
  18. Is it possible to std::move objects out of functions? (C++11)
  19. Why do some people use swap for move assignments?
  20. How can I use something like std::vector?
  21. Non-copyable elements in vector
  22. Can I typically/always use std::forward instead of std::move?
  23. Compile time triggered range check for std::vector
  24. Is a `=default` move constructor equivalent to a member-wise move constructor?
  25. Why can’t I create a vector of lambdas (of the same type) in C++11?
  26. Why doesn’t emplace_back() use uniform initialization?
  27. Move or Named Return Value Optimization (NRVO)?
  28. Should all/most setter functions in C++11 be written as function templates accepting universal references?
  29. Move semantics == custom swap function obsolete?
  30. Move constructor on derived object

Leave a Comment