Intermediate C++ Game Programming Tutorial 20

In this video we learn about r-value reference and move semantics, which is perhaps the most important feature that was added in the C++11 update. This is going to allow us to manage and transfer our resources in a precise and efficient manner. It is sexy as fuck and I love it.

Topics Covered

• r-values and l-values
• r-value reference function overloading
• Move constructor and move assigment
• Rule of 5
• std::move
• std::make_move_iterator

Video Timestamp Index

Tutorial 20

[Expand]

• Why are move semantics important and required? 0:23

• • Example use case: adding objects to a container using emplace_back
  • Instead of deep copying every element of the container when expanding the container capacity, move semantics allow you to direct pointers in the new container to existing blocks of memory

• What is an rvalue (simple definition) 2:48

• • rvalues are values that can only appear on the right hand side of an assignment operation (=), such as:

  - literals; 69 = 420; is invalid

  - temporary return values of functions; f() = 420;, where the signature of f is int f();, is invalid

  • lvalues are values that can appear on the left hand side of assignments; they can be assigned to, for example:

  - x = 10; if x has been declared as int x;

  - obj.Get() = 69; if the member function Get() returns a reference to an integer member variable

  - arr[3] = 10; if arr has been declared as an array of integers

• Why is the distinction between rvalues and lvalues useful? 4:57

• • The ability to detect whether a function is called with an rvalue (rather than with an lvalue) is useful, because the function can freely mangle an rvalue as it will be destoyed after the function call anyway

• Overloading a function to take an rvalue reference using && 6:11

• • Using the && declarator in a function signature, e.g. void SomeFunc(SomeType&& donor)
  • This makes the compiler dispatch a function call to the overloaded version when an rvalue is passed
    (note: && was added in c++11; & is the familiar lvalue reference declarator)

• std::move(): Converting a variable into an rvalue reference 8:00

• • This will allow the function to steal/use the resource(s) that are passed in
  • This can be useful if you don't need those resources anymore
  • std::move(someVar) is shorthand (from the STL) for the static cast static_cast<Type&&>(someVar)
  • All the STL containers are already wired up to be able to take advantage of "move semantics"

  - For example: std::string a = std::move(b) will leave b (also a std::string) empty after execution

  - There is no magic to this call; all it does is pass b as an rvalue reference, calling the overloaded constructor (the "move constructor"), and the overloaded assignment operator ("move assignment") of std::string in which the contents of b are passed over to a and removed from b.

• Move constructor and Move assignment 10:07
  • The STL containers will try to use move semantics as much as possible
  • To benefit from this, any custom classes (or rather: any Type) will need to define a move constructor and a move assignment operator
  • std::move will default to the normal (lvalue reference) constructor and assignment operator if their move (rvalue reference) counterparts are not defined
• Implementing the move constructor and move assignment operator in the Surface class of the Sprite drawing project 11:09
• WORK-IN-PROGRESS

Note

If you are using Visual Studio 2017, you might notice that our move members are not being used during std::vector growth even after we have 'properly' implemented them. This is expected, so don't pay it much mind at the moment.

The reason for this is that std::vector will only use the move members if they are guaranteed not to throw any exceptions (as per the standard). This issue will be dealt with in Intermediate 22 (tutorial on exceptions). For your interest, you can enable the move optimization by declaring your move ctor as Surface( Surface&& ) noexcept. The same should be done for the move assignment and the destructor.

You might wonder why Chili had no problems in the video. In the video, Chili was using Visual Studio 2015, which does not conform to the standard in this point, so it uses the move members regardless of whether or not they are marked noexcept.

Source Code

• Sprite Github Repository (for Surface code)
  

See also

• Next in series (Tutorial 21)
• Intermediate C++ Game Programming Series