3 ms·
I've been using C++ about as long as OP, and I found much of C++11 to be practical and useful so adopted the useful bits into my tool chest. Since then, the add
by ryandrake 6y ago
I've been using C++ about as long as OP, and I found much of C++11 to be practical and useful so adopted the useful bits into my tool chest. Since then, the additions seem (to me) to be more academic and interesting to computer scientists, so I haven't really found the need to keep up. I think C++11 hit the sweet spot. Threading, Smart pointers, std::unordered_xxx hash tables, strongly typed enums, lambda functions, are great and useful. Tuples, initializer lists, range-based for loops, type inference are convenient, I don't see how they hurt. R-value references and constexpr are neat academically, but I've so far failed to see the practical killer app for them, or how they could improve my existing code. The rest of C++11, I either haven't looked into or just haven't been convinced make my code better than without.
- FartyMcFarter 6y ago> R-value references ... are neat academically, but I've so far failed to see the practical killer app for them, The killer app is unique_ptr. Without move semantics, unique_ptr wouldn't be nearly as nice to use. There's a good reason that it has a move constructor but not a copy constructor.
- FartyMcFarter 6y agoThat and of course improved performance by avoiding copies where they aren't needed. This is easily benchmarkable in practice.