Should all/most setter functions in C++11 be written as function templates accepting universal references?

by

You know the classes A and B, so you know if they are movable or not and if this design is ultimately necessary. For something like std::string, it’s a waste of time changing the existing code unless you know you have a performance problem here. If you’re dealing with auto_ptr, then it’s time to rip it out and use unique_ptr.

It’s usually preferred now to take arguments by value if you don’t know anything more specific- such as

void set_a(A a) { _a = std::move(a); }

This permits the use of any of the constructors of A without requiring anything except movability and offers a relatively intuitive interface.

More Related Contents:

  1. Can I typically/always use std::forward instead of std::move?
  2. What is “rvalue reference for *this”?
  3. How to enforce move semantics when a vector grows?
  4. C++11 rvalues and move semantics confusion (return statement)
  5. initializer_list and move semantics
  6. When should std::move be used on a function return value? [duplicate]
  7. What is the advantage of using forwarding references in range-based for loops?
  8. Reusing a moved container?
  9. What does the standard library guarantee about self move assignment?
  10. Is a moved-from vector always empty?
  11. Is there a difference between universal references and forwarding references?
  12. How to actually implement the rule of five?
  13. Does moving leave the object in a usable state?
  14. Why do we copy then move?
  15. Should I delete the move constructor and the move assignment of a smart pointer?
  16. copy vs std::move for ints
  17. Why do you use std::move when you have && in C++11? [duplicate]
  18. What are the main purposes of std::forward and which problems does it solve?
  19. Do built-in types have move semantics?
  20. Is there any case where a return of a RValue Reference (&&) is useful?
  21. When to make a type non-movable in C++11?
  22. What does `auto && e` do in range-based for-loops?
  23. Is std::array movable?
  24. Should the Copy-and-Swap Idiom become the Copy-and-Move Idiom in C++11?
  25. Move out element of std priority_queue in C++11
  26. Why does std::forward have two overloads?
  27. How does std::forward receive the correct argument?
  28. C++: std::move with rvalue reference is not moving contents
  29. What is std::move(), and when should it be used and does it actually move anything?
  30. Move constructor on derived object

Leave a Comment