2015 C++ Hot! Review

Here are the most likely interpretations and how they relate to C++ in 2015:

// Factory function using C++11/14 unique_ptr std::unique_ptr<Piece> createPiece() { return std::make_unique<Pawn>(); // make_unique introduced in C++14 } 2015 c++

Concepts, modules, and networking were years away (C++20 eventually delivered some of these). And the ecosystem was still fractured: Microsoft's ABI break for std::string in VS2015 caused real headaches. Here are the most likely interpretations and how

Finally completing the smart pointer pair and making "no raw new " a realistic coding standard. 2. The Rise of the C++ Core Guidelines createPiece() { return std::make_unique&lt

#include <string> #include <memory>

2015 was not a utopia. Compile times were still awful. Error messages from templates—especially with std::bind or deeply nested types—remained Lovecraftian. The lack of a standard package manager meant every project had its own third_party/ folder filled with Git submodules.