3 ms·
I disagree? Functions which allocate things returning unique_ptr is much clearer than returning a raw pointer. Clear ownership being passed, as opposed to may
by Tyr42 9y ago
I disagree? Functions which allocate things returning unique_ptr is much clearer than returning a raw pointer. Clear ownership being passed, as opposed to maybe just having a view into some internal buffer.
I mean, if you only view functions as being called for side effects, then yeah maybe. But if you're constructing a data pipeline, unique_ptr in and out makes a lot of sense.
- Koshkin 9y agoSure, and that is a special case I was referring to. (Another one would be a class factory method returning a unique pointer to an interface.) In general, though, passing a unique_ptr around is a bit cumbersome as this requires calling std::move way too often.