ptc-print VS OpenfoldersBaseProject

Repository link: https://github.com/JustWhit3/ptc-print

Hello everybody, I want to present you `ptc-print`, a modern C++ library for custom printing to the output stream. It is basically a detailed implementation of the Python `print()` function, with several additions. It is **NOT** a formatting library as `fmt`, but a pretty printer tool which provides you a most comfortable way to print generic stuff to the output stream. In particular, some of its features are: - It is constructed through the `Print` functor, which is a fully type- and thread-safe class with automatic memory management, implemented through an *header-only* library, with no external dependencies. - It supports also the usage of *ANSI escape sequences*. - It supports the printing of all the standard types and also stdlib ones (`std::vector`, `std::map` etc...). - It is possible to choose to print using different char types (`char`, `wchar_t`...). - Several [advantages](https://github.com/JustWhit3/ptc-print#advantages) with respect to similar libraries (friendly syntax, better performances, etc...). There is a whole README section dedicated to this. It has also many more features like the possibility to choose end and separator characters (like in Python) or to set a pattern among each printed argument. In the main README you can find all the information you want, a list of todo stuff and some preliminary [benchmarking](https://github.com/JustWhit3/ptc-print#comparison-with-other-libraries) studies I performed with respect to other similar libraries. With [performance improvements](https://github.com/JustWhit3/ptc-print#performance-improvements) options enabled it is even consistently faster than `fmt::print` or `printf`. If you like the repo don't forget to leave a star on GitHub! Thanks. Repository link: https://github.com/JustWhit3/ptc-print

Repository: https://github.com/JustWhit3/ptc-print

*Makes angry noises about cmake presets(shamelessplug)*

Our project utilizes vcpkg to consume all libs we require, even those that are not available on vcpkg repo via overlays. What is nice about overlays is that it allows you to add your own cmake patches to the lib you're consuming which means you can write your own cmake layer for non-cmake libs (ie. bazel based projects, we use it for tensorflowlite), this is pretty much our setup, although this example doesn't show the overlay part