Skip to main content

Timeline for Using std::unique_ptr and std::move

Current License: CC BY-SA 3.0

7 events
when toggle format what by license comment
May 23, 2017 at 12:40 history edited CommunityBot
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Nov 22, 2014 at 23:42 comment added Goswin von Brederlow As to std::make_unique. My c++ reference has std::unique_ptr(...) as constexpr so it is safe to use without exceptions. No such garantee on std::make_unique. Plus that needs a constructor which often conflicts with the dependency inversion and create factories in this code. Otherwise I will use it though.
Nov 22, 2014 at 23:37 comment added Goswin von Brederlow "Inpoc::create should actually be a regular constructor." It can't be a normal constructor since I need to be able to signal errors. The existing code is using dependency inversion instead of creating dummy objects with is_good() functions. Changing that would be a major redesign.
Nov 22, 2014 at 23:34 comment added Goswin von Brederlow "The main point of unique_ptr is that it eliminates ownership problems." That is exactly what I want to do.
Nov 22, 2014 at 21:21 history edited nwp CC BY-SA 3.0
added 99 characters in body
Nov 22, 2014 at 21:14 history edited nwp CC BY-SA 3.0
Corrected another mistake
Nov 22, 2014 at 20:56 history answered nwp CC BY-SA 3.0