scnlib VS libflow

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 :)

Have you seen libflow? It's also built on the same model (Rust-style iterators), curious how they compare.

Just to get on the bandwagon: here are my C++20 Advent of Code solutions, mostly using my work-in-progress Flow library

Perhaps relevant since Barry mentioned my Flow library as an example: the following (written a couple of years ago for another Reddit thread) is what would appear in Flow's documentation as a justification for using optional references -- if Flow actually had any documentation, that is...

If you want to use the Rust iterator model in C++, then you can do so.

I have a work-in-progress-for-a-long-time-now functional-style programming library called libflow, which uses Swift/Rust style iterators. It has optional support for coroutines ("flowroutines", heh) which can make writing "one-shot" iterators very simple indeed.