scnlib VS AnyAny

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

https://github.com/kelbon/AnyAny trait(add, void(int), self.add(args...));

i dont know what he means, but with this type erasure library you can have non virtual interface and still use dynamic polymorphism with those types, so you dont need choose *do i need to do this type polymorphic* etc

There are also invoking from tuple and curring (just an example of technique)https://github.com/kelbon/AnyAny/blob/main/examples/functional_paradigm.hpp

As for my example containers: https://github.com/kelbon/AnyAny/blob/main/include/data_parallel_vector.hpp

variant_swarm - container which behaves as set of std::variant, but with much faster visit operation and operation for getting view to all values of type T. It short, it just stores all types separatelly and supports operations visit, view, also you can change underlying containers for Ts..., it is std::vector by default https://github.com/kelbon/AnyAny/blob/main/include/variant_swarm.hpp

Its part of my library for working with polymorphic types.

Good idea selling Rust from behind enemy lines soldier! My god, your readme doesn't even mention Rust, wonderful!

https://github.com/kelbon/AnyAny here you can see how it implemented, for example