Current Proposals for C++17

Re:Current Proposals for C++17 by danbolt on Thursday February 25, 2016 @08:19PM (#11179237)

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.

[ Parent | on HN ]

Re:Current Proposals for C++17 by Kristine1975 on Friday February 26, 2016 @01:59AM (#11180177)

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 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.

[ Parent | on HN ]