PassingByValue.dox 1.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  1. namespace Eigen {
  2. /** \eigenManualPage TopicPassingByValue Passing Eigen objects by value to functions
  3. Passing objects by value is almost always a very bad idea in C++, as this means useless copies, and one should pass them by reference instead.
  4. With %Eigen, this is even more important: passing \ref TopicFixedSizeVectorizable "fixed-size vectorizable Eigen objects" by value is not only inefficient, it can be illegal or make your program crash! And the reason is that these %Eigen objects have alignment modifiers that aren't respected when they are passed by value.
  5. For example, a function like this, where \c v is passed by value:
  6. \code
  7. void my_function(Eigen::Vector2d v);
  8. \endcode
  9. needs to be rewritten as follows, passing \c v by const reference:
  10. \code
  11. void my_function(const Eigen::Vector2d& v);
  12. \endcode
  13. Likewise if you have a class having an %Eigen object as member:
  14. \code
  15. struct Foo
  16. {
  17. Eigen::Vector2d v;
  18. };
  19. void my_function(Foo v);
  20. \endcode
  21. This function also needs to be rewritten like this:
  22. \code
  23. void my_function(const Foo& v);
  24. \endcode
  25. Note that on the other hand, there is no problem with functions that return objects by value.
  26. */
  27. }