spdlog VS strf

Why a new lib instead of using or contributing to an existing one as spdlog?

https://github.com/gabime/spdlog

GitHub repo: gabime/spdlog

SpdLog https://github.com/gabime/spdlog

The usual recommendation when logging libraries are brought up is spdlog, which is however header-only. It's available on Conan-center.

* Aha! In digging up the docs for NDC, I found this[1], which does mention a book for your reading list: "Patterns for Logging Diagnostic Messages" part of the book "Pattern Languages of Program Design 3" edited by Martin et al.

[1] https://github.com/gabime/spdlog

FetchContent_Declare( spdlog GIT_REPOSITORY https://github.com/gabime/spdlog GIT_TAG origin/v1.x ) FetchContent_MakeAvailable(spdlog)

Typically, you'd use a logging library to handle stuff like this. I personally like spdlog. You use different logger functions (info, warn, error) and depending on what level you have set for the logger (or globally) some of the functions become no-ops. E.g. When not running in verbose mode all spdlog::info() do nothing.

You might get interested in trying strf library instead:

If you want a formatting library that supports well char8_t and UTF, you might get interested in the one I'm developing: Strf.

You might like the strf formatting library then

You can also use https://github.com/robhz786/strf to convert utf-8 to utf-32 ( as demonstrated here).

Format strings enable the use of tools like gettex. However, with the strf formatting library, It is possible to use them without a format string.

So it is a formatting library (strf), and if one wants to make a type xyz printable, one can either specialize a template or overload tag_invoke function, like below:

The Strf formatting library may solve your problem:

There is the strf formatting library. Its current version (0.14) is not working well in CUDA, but I'm working to fix this into the next release, which should come soon. The usage would be:

strf