Externally indexed torrent

If you are the original uploader, contact staff to have it moved to your account

Textbook in PDF format

The idea of the Notebook C   series is to share some tips and tricks about various C   elements. All books in this series are somewhat short and small books, one for each major topic. Such that the paperback version can be carried around easily.
This part of the series is all about move semantics. I will introduce the feature to you in an maybe unconventional but easy-to-understand way. Move semantics are nothing special, afterall.
We'll start looking at what move semantics is, how it works, and why we should most times stay away from std::move. We establish some rules about when to use std::move, when std::forward. You learn about why not to move return values or temporary objects. You want to get the best speed from your custom data type and the STL? No problem, you will learn what your class must look like to achieve this.
In the end, you also learn about some feature that is not seen that often, ref-qualifiers, how they work, why they are there, and when to use them.
All in all, after having read this book, you have a solid understanding of move semantics.
Before diving in with various other tips, let’s get the fundamental understanding of move semantics in C  .
In programming languages in general, we have two different types of move semantics:
- destructive move
- non-destructive move
In C  , we have the latter, but let’s look into the first form first. A destructive move means that once we move an object, we will see later what that means and how to do it in C  , the source object gets destroyed afterward. The destructive move approach has a couple of advantages. One of the biggest questions about move semantics in C   is about the so-called moved-from state, which you learn about in Note 9