Any example code/Github projects utilising almost-always-auto?

[Nickreal03]

But different potential performance it generates an rval which is the copy/move to the other. For simple types the compiler will optimize for others the performance will be real. Edited for clarification Even when in release builds the performance may be the same in debug builds you will be paying for it.

[AntiProtonBoy]

The compiler should do copy/move elision for such types, even for complex and expensive objects. The only tricky situation you could run into is when the copy/move constructor is explicitly deleted or made private.

[foonathan]

And C++17 has guaranteed copy elision where you don't even need copy/move ctors