Created attachment 256718 [details] [PATCH] [NEW PORT] devel/reflect-cpp: C++-20 library for fast serialization, deserialization and validation reflect-cpp is a C++-20 library for fast serialization, deserialization and validation using reflection, similar to pydantic in Python, serde in Rust, encoding in Go or aeson in Haskell. reflect-cpp fills an important gap in C++ development. It minimizes boilerplate code and enhances code safety for seamless and efficient data exchange across system components. Design principles for reflect-cpp include: Close integration with containers from the C++ standard library Close adherence to C++ idioms Out-of-the-box support for JSON Simple installation Simple extendability to other serialization formats Simple extendability to custom classes Being one of the fastest serialization libraries in existence, as demonstrated by our benchmarks Poudriere testport: OK for [amd64 i386] * [142 141 134] Make test: 100% tests passed, 0 tests failed out of 193
What ports will use this library?
(In reply to Vladimir Druzenko from comment #1) What ports will use this library? I made it for any port who would like to.
This makes little sense. There are thousands of different small libraries. Simply adding them all would only increase the load on committers without any benefit. Sometimes we don't have time to commit even trivial updates from maintainers: https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=365 There is even a practice of removing a library from ports if there is not a single port left that uses it. Therefore, I would not add just a library without consumers. This does not apply to ports that contain, in addition to the library, some software that uses this library. This also applies to the other two PRs: https://bugs.freebsd.org/284063 https://bugs.freebsd.org/284070
Yes, I may understand the committers being overloaded. Why couldn't then maintainers do commit at least trivial update patches by themselves? This would offload a lot of work from the committers to be able to focus on more difficult/important things…
I already had this idea: somehow allow some maintainers to commit to their ports themselves. It's something between just a port maintainer and a committer to ports. But I can't imagine how to implement it both organizationally and technically.