std::for_each(v.begin(), v.end(), [](int x) { std::cout << x * 2 << "\n"; }); Smart pointers ( unique_ptr , shared_ptr ) moved from "Boost-only magic" to standard-issue memory safety. Raw new and delete started looking like exposed wiring in a modern home. But let’s not rewrite history. C++ in 2013 still had teeth—and fangs. Move semantics were powerful, but the rules for when a move happens vs. a copy were arcane enough to require a PhD in "value category theology" (lvalues, rvalues, xvalues, glvalues, prvalues... shudder ).
⭐⭐⭐⭐ (one star removed for template error messages longer than War and Peace ) 2013 c++
2013 was the year C++ stopped being your dad’s systems language and started flirting with modernity. The ISO standard known as C++11 (published late 2011) had finally trickled down from compiler god-mode to everyday build systems. GCC 4.8.1 was solid. Clang 3.3 was a revelation. Even Visual Studio 2013— yes, Microsoft —started playing catch-up with real move semantics and variadic templates. Let’s start with auto . In 1998, auto was a joke—a keyword that meant "please ignore me." In 2013, auto meant finally, I don't have to type std::vector<std::unique_ptr<Foo>>::const_iterator like a medieval scribe . std::for_each(v
auto it = my_map.find(key); // The angels sang. Range-based for loops? We had them. Lambda expressions? Oh yes—and they could capture [this] , [=] , [&] , or your entire will to live. C++ in 2013 still had teeth—and fangs