Sane C++ Libraries

1. SaneCppLibraries

   1 3 555 9.5 C++

   Platform Abstraction C++ Libraries

   

   That's why I am currently against its use, unless there is a very special case.

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

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. json_test_data

   2 26 14 0.0

   Test data for nlohmann/json

   

   https://github.com/nlohmann/json

   I used this for JSON last time I wrote any C++ a few years ago and it still seems popular. It seemed sane enough to me.

4. abseil-cpp

   3 61 15,780 9.7 C++

   Abseil Common Libraries (C++)

   

5. serenity

   4 263 31,562 10.0 C++

   The Serenity Operating System 🐞

   

   https://github.com/SerenityOS/serenity

   The best way to write proper exception free C++ is not to use the C++ Standard Library.

6. UnrealEngine

   5 124 - -

   > you can still use it with smart pointers provided by any other library

   Is the point of having a kitchen-sink library like this not that you dont have to reach for a 3rdparty library for things that you need 'all the time'?

   Certainly, not everyone needs it.

   ...but, not everyone needs threads either. Not everyone needs an http server; and yet, if you have an application framework that provides them, when you do need them, it saves you reaching for yet-another-dependency.

   Was that no the point from the beginning?

   unique_ptr is a fundamental primitive for many, as you see from some other frameworks (1), and implementation is not always either a) trivial, or b) as simple as 'just use std::unique_ptr'.

   This does seem like a very opinionated decision with reasonably unclear justification.

   [1] - eg. https://github.com/EpicGames/UnrealEngine/blob/release/Engin..., https://github.com/electronicarts/EASTL/blob/master/include/...

7. EA Standard Template Library

   6 43 8,621 4.0 C++

   EASTL stands for Electronic Arts Standard Template Library. It is an extensive and robust implementation that has an emphasis on high performance.

   

   > you can still use it with smart pointers provided by any other library

   Is the point of having a kitchen-sink library like this not that you dont have to reach for a 3rdparty library for things that you need 'all the time'?

   Certainly, not everyone needs it.

   ...but, not everyone needs threads either. Not everyone needs an http server; and yet, if you have an application framework that provides them, when you do need them, it saves you reaching for yet-another-dependency.

   Was that no the point from the beginning?

   unique_ptr is a fundamental primitive for many, as you see from some other frameworks (1), and implementation is not always either a) trivial, or b) as simple as 'just use std::unique_ptr'.

   This does seem like a very opinionated decision with reasonably unclear justification.

   [1] - eg. https://github.com/EpicGames/UnrealEngine/blob/release/Engin..., https://github.com/electronicarts/EASTL/blob/master/include/...

Suggest a related project