Smart pointers realy need a native way to be specified, similar to how we use & ...

johannes1234321 · on Jan 20, 2017

A common way is having a "using FooPtr = shared_ptr<Foo>" somewhere and then only use FooPtr. This also reduces the occurrences in that word cloud.

ddavis · on Jan 20, 2017

> This also reduces the occurrences in that word cloud

Ah, yes, very good point.

radupopescu · on Jan 20, 2017

Nowadays, you can do:

    auto sh_ptr = make_shared(....); // Since C++11

or

    auto uniq_ptr = make_unique(....); // Since C++14

It saves you from having to explicitly name the type parameter and you just need to pass in the parameters of the constructor. It's not as terse as & or *, but it's not that bad.

ddavis · on Jan 20, 2017

I agree it's made C++ a bit verbose, though something like the using keyword helps (which is 30 spots below typedef!)