SaneCppLibraries

For me personally SharedPtr is very rarely needed as it encourages building difficult to untangle ownership hierarchies. I did use a lot of Shared Ptr in the past when creating a node.js like library in C++ but breaking the ref cycles everywhere was needed has always been a pain. That's why I am currently against its use, unless there is a very special case. Regarding UniquePtr<T> I used to have one but I later on decided to remove it. https://github.com/Pagghiu/SaneCppLibraries/commit/9149e28 However, that being said the library is lean enough so that you can still use it with smart pointers provided by any other library (including the standard one) if that's your preference.