Intermediate C++ Game Programming Tutorial 20 - Revision history

R vdw: /* Video Timestamp Index */

2019-10-31T20:49:58Z

‎Video Timestamp Index

2019-10-21T02:18:39Z

‎Note

2019-10-20T20:44:24Z

‎Video Timestamp Index

2019-10-20T20:41:33Z

‎Video Timestamp Index

2019-10-20T20:25:17Z

‎Video Timestamp Index

2019-10-20T20:21:10Z

‎Video Timestamp Index

2019-10-20T20:14:34Z

‎Video Timestamp Index

2019-10-20T20:13:49Z

‎Video Timestamp Index

2019-10-20T20:12:03Z

‎Video Timestamp Index

2019-10-20T19:59:34Z

‎Video Timestamp Index

@@ Line 88: / Line 88: @@
 ** Elegant way of being able to move resources from one container into another
 ** Lets us create Types that cannot be copied, but that can still be moved: unique non-copyable types (no duplicates can exist), but that you can still have in a container, have that container grow, or move objects around from one container to the other
-** Move semantics enable the concept of smart pointers (<code>unique_ptr</code>, the most important smart pointer, is a type that has the above characteristics (next up in Tutorial 21)
+** Move semantics enable the concept of smart pointers (<code>unique_ptr</code>, the most important smart pointer, is a type that has the above characteristics (next up in Tutorial 21))
 </div>
 </div>

@@ Line 93: / Line 93: @@
 == Note ==
-If you are using Visual Studio 2017, you might notice that our move members are not being used during <code>std::vector</code> growth even after we have 'properly' implemented them. This is expected, so don't pay it much mind at the moment.
+If you are using Visual Studio 2017+, you might notice that our move members are not being used during <code>std::vector</code> 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 <code>std::vector</code> 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 <code>Surface( Surface&& ) noexcept</code>. The same should be done for the move assignment and the destructor.

@@ Line 43: / Line 43: @@
 ** All the STL containers are already wired up to be able to take advantage of "move semantics"
 *:- For example: <code>std::string a = std::move(b)</code> will leave <code>b</code> (also a std::string) empty after execution
-*:- There is no magic to this call; all it does is pass <code>b</code> as an rvalue reference, calling the overloaded constructor (the "move constructor"), and the overloaded assignment operator ("move assignment") of <code>std::string</code> in which the contents of <code>b</code> are passed over to <code>a</code> and removed from <code>b</code>.
+*:- There is no magic to this call; all it does is pass <code>b</code> as an rvalue reference, calling the overloaded copy constructor (the "move constructor"), and the overloaded assignment operator ("move assignment") of <code>std::string</code> in which the contents of <code>b</code> are passed over to <code>a</code> and removed from <code>b</code>.
 </div>
 *  Move constructor and Move assignment [https://youtu.be/93mlQnWbyuk?t=10m07s 10:07]

@@ Line 14: / Line 14: @@
 * Why are move semantics important and required? [https://youtu.be/93mlQnWbyuk?t=0m23s 0:23]
 <div class="mw-collapsible-content">
-** Example use case: adding objects to a container using <code>emplace_back</code>
+** Example use case: adding objects to a container using <code>std::vector::emplace_back</code>
 ** 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
 </div>

@@ Line 85: / Line 85: @@
 * Recap: why move semantics are neat and lead into smart pointers
 <div class="mw-collapsible-content">
-** Move semantics: one of the most important additions that came with C++11. The funcntionality gives us finer control over how our resources are managed, and we can re-use resources of objects that would otherwise be discarded/deleted
+** Move semantics: one of the most important additions that came with C++11. The functionality gives us finer control over how our resources are managed, and we can re-use resources of objects that would otherwise be discarded/deleted
 ** Elegant way of being able to move resources from one container into another
 ** Lets us create Types that cannot be copied, but that can still be moved: unique non-copyable types (no duplicates can exist), but that you can still have in a container, have that container grow, or move objects around from one container to the other
-** Move semantics enable the concept of smart pointers (unique_pointers, the most important smart pointer, is a type that has the above characteristics (next up in Tutorial 21)
+** Move semantics enable the concept of smart pointers (<code>unique_ptr</code>, the most important smart pointer, is a type that has the above characteristics (next up in Tutorial 21)
 </div>
 </div>

@@ Line 72: / Line 72: @@
 *:: if the default function is defined as <code>void SomeFunc(const std::string& str)</code>, <br />just use a single <code>void SomeFunc(std::string str)</code> that takes (in this example) a string by value
 *:- If an lvalue is passed as the argument, the string will be copied into the local variable
-*:- If an rvalue is passed as the argument, the string will be move the data into the local variable
+*:- If an rvalue is passed as the argument, the string will be moved into the local variable
 </div>
 * Fix the <code>Surface</code> class to include the case (or: the state) where a surface is empty [https://youtu.be/93mlQnWbyuk?t=19m09s 19:09]

@@ Line 57: / Line 57: @@
 </div>
 * The full story on implicit compiler definition of special member functions and the "Rule-of-5" [https://youtu.be/93mlQnWbyuk?t=14m22s 14:22]
 ** If you implement any of the special member functions, you should implement all of them:
 *:- Destructor
@@ Line 63: / Line 64: @@
 *:- Move constructor
 *:- Move assignment
 * The behavior of the default move members and the "Rule-of-0" [https://youtu.be/93mlQnWbyuk?t=15m17s 15:17]
 <div class="mw-collapsible-content">

@@ Line 16: / Line 16: @@
 ** Example use case: adding objects to a container using <code>emplace_back</code>
 ** 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
 </div>
 * What is an rvalue (simple definition) [https://youtu.be/93mlQnWbyuk?t=2m48s 2:48]
@@ Line 79: / Line 75: @@
 ** The <code>make_move_iterator</code> is a convenience function that constructs a <code>std::move_iterator<Iter>(i)</code> which can be used to move out from the elements accessed through the input iterator <code>i</code>
 ** Example code written to move strings from a vector of strings when they are larger than a certain threshold
 </div>