3 ms·

C++14 just cleaned up a couple of minor things from C++11. It was essentially intended to be a point release. C++17 is the first "big" standard change since C+

• petra 11y ago
  Wasn't a lot of memory safety and thread safety introduced in c++14?
  • msbarnett 11y ago
    C++11 introduced threading and a memory model for C++. C++14 had relaxed requirements on constexpr, initializers in lambda captures, using auto for return type deductions, and a few other small tweaks.
  • danbolt 11y ago
    C++11 had unique_ptr and shared_ptr, but C++14 helped with adding make_unique. In my opinion, that makes a big difference because now making a special unique pointer is an atomic operation in your program.
    • Kristine1975 11y ago
      If only make_unique (and make_shared) worked with uniform initialization... struct Foo { int i; float f; bool b; // No constructor }; std::make_unique<Foo>(1, 2.3f, true); Doesn't compile, since make_unique requires an appropriate constructor (see https://isocpp.org/files/papers/n3588.txt https://isocpp.org/files/papers/n3588.txt for the rationale). It also doesn't work when Foo's constructor is private, even when called from a function that would have access to this private constructor. And this is my beef with C++: Yes it's powerful, and I quite like it, but you sooner or later hit these speed bumps that unnecessarily complicate things.