Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • python-codegen
  • 6.x protected
  • llvm-15
  • julia-6.4.0
  • julia
  • julia-meson
  • 5.x protected
  • julia-6.3.0
  • 4.6 protected
  • uop
  • rework_pac
  • aux_vars_fix
  • julia-6.2.0
  • created_preprocessor_repo
15 results

DataTree.hh

Blame
    • Sébastien Villemot's avatar
      27952078
      No longer delete move constructor/assignment operator · 27952078
      Sébastien Villemot authored 
      We follow the advice given by Josuttis in his book about move semantics.

Deleting those member fuctions can be a bug if we want to allow copy semantics,
because overload resolution will no longer fallback to the copy
constructor/assignment operator when given an rvalue.

In particular, this explain why it was not possible to delete the move
assignment operator of the StaticModel class.
      27952078
      History
      No longer delete move constructor/assignment operator
      Sébastien Villemot authored 
      We follow the advice given by Josuttis in his book about move semantics.

Deleting those member fuctions can be a bug if we want to allow copy semantics,
because overload resolution will no longer fallback to the copy
constructor/assignment operator when given an rvalue.

In particular, this explain why it was not possible to delete the move
assignment operator of the StaticModel class.