Nothing is better than copy or move - Roger Orr [ACCU 2018]

C++11 introduced 'move semantics' to facilitate transferring the contents of one object to another more efficiently than creating a copy and then erasing the original. This is particularly focussed on optimising the performance of temporary objects, such as when passing them into or out of a function call.
However, in all the discussions about copying and moving it is easy to forget that not creating an object in the first place may be even more efficient. This can be something done by design choice, or an optimisation applied during compilation. For example, introduction of a temporary object by copying can be removed; this is is called 'copy elision' in C++ and has been permitted in the language for many years.
C++17 adds some additional specification around the creation of temporary variables with the phrase 'temporary materialization'.
This presentation will look at some 'worked examples' of how this behaves in practice, and some things to be aware of.

[@mjKlaim]

Just wanted to say that your fixes of the different videos have been noticed and appreciated. Thanks for the effort, I know it's a lot of time to spend in.

[@ACCUConf]

Thats very kind of you to say, we put a lot of effort into producing the videos, but with between 60-80 talks all averaging 1hr and 30 minutes its difficult to review all of the talks in their entirety.

[@mjKlaim]

No problem, I think as long as you react to feedback it's fine. You have been very fast, fast enough for me to remark :)

[@cgoobes]

Awesome job though. There is one slide you missed ( the one after the 32 bit 64 bit slide around the 57:30 marker about the linux stuff ).

[@tebes9265]

In contrast to what is being said in the talk, temporary materialization does NOT occur when initializing an object from a prvalue of the same type. Such objects are directly initialized by the prvalue. He is talking about the same concept, but e.g. saying "temporary materialization into x" (~ 44:00) is just misleading as there is no temporary materialization involved. Refer to cppreference (temporary materialization), for example.

[@max0x7ba]

Quite insightful about copying.

[@FranciscoCrespoOM]

Very meaningful!

[@hl2mukkel]

Great talk!

[@aaronmacdougall]

C++ has become so complicated. None of this nonsense is necessary to write good code.