scnlib VS think-cell-library

scnlib (https://github.com/eliaskosunen/scnlib) scanf

include(FetchContent) FetchContent_Declare( Catch2 GIT_REPOSITORY https://github.com/catchorg/Catch2.git GIT_TAG v3.0.0-preview4 ) FetchContent_Declare( fmt GIT_REPOSITORY https://github.com/fmtlib/fmt.git GIT_TAG 9.1.0 ) FetchContent_Declare( scnlib GIT_REPOSITORY https://github.com/eliaskosunen/scnlib.git GIT_TAG v1.1.2 ) FetchContent_MakeAvailable(Catch2 fmt scnlib)

Yeah, but parsing format strings in runtime induces an overhead, and doing it in compile time is not trivial, and I’m not sure ClearIO is worth the trouble, since it turns out scnlib exists.

The code is rather nice (in my biased opinion) and makes heavy use of a couple of libraries like scnlib and [Eigen](eigen.tuxfamily.org/). Some things could probably be more optimized but I mainly focused on conciseness. I hope this is useful and I can explain my thought process further if you have any questions.

I've found https://github.com/eliaskosunen/scnlib but haven't tested it. Maybe that suits your needs for 2.

I had a user enum like enum class Color {Red, Green, Blue}; that I wanted to add serialization support for. Following the docs (https://scnlib.readthedocs.io/), after some tweaks I arrived at the following:

Thanks for the comment, I made an issue tracking this: https://github.com/eliaskosunen/scnlib/issues/51

I am using some modern libraries: scnlib fmtlib Eigen and usually abuse lambdas :)

We at think-cell use that pattern a lot in our library.

Library * We use Boost throughout our code, e.g., Boost.Spirit for parsing. * We have our own range library, in the same spirit as Boost.Range or Eric Niebler’s range-v3, but going further, for example, by unifying internal and external iteration. We gave a talk about it, and most of the code is public. * We develop our own cross-platform library to support Mac and Windows with a single code base. * We have our own reference-counting and persistence libraries to save and restore whole object trees. * We have an extensive bug reporting infrastructure. Assertions and error checks stay in the release code, and our software automatically reports bugs to our server. The server analyzes the bug, categorizes it and files it in a database that all developers can access. If an update fixes the bug, the user can download the update directly from a bug response web page.