Folly is a heavy dependency

[jpc0]

All of folly is being pulled in for:

• folly::SharedMutex
• folly::Synchronized
• folly::F14Set
• folly::F14Map
• folly::CPUThreadPoolExecutor

I'm not going to pretend I have solutions to this but it might be possible that some of this could be replaced with boost libraries / stdexec or even the stdlib version. Boost is easier since modern boost is CMake native and you don't necessarily need to pull in all of boost. stdexec is the reference implementation for std::execution which has been included in the C++26 standard but might need some refactoring of existing code.

Folly pulls in quite a few boost libraries as well as some google libraries and fmtlib.

[efecan0]

Totally agree I’ve decided to remove Folly entirely in the next version.

I’m already replacing the thread pool and F14 maps, but still figuring out good alternatives for folly::Synchronized and SharedMutex that won’t hurt performance or safety too much.

If you have any suggestions or experience with good drop-in replacements, I’d love to hear them!

[jpc0]

I would need to dive deeper into the code. I generally try to avoid synchronization where possible and will rather build lock free / wait free when needed, so when I do use synchronization I am fine with std::mutex.

[efecan0]

If you do decide to dive deeper, I’ve kept the project fully compatible with Doxygen all public classes and methods are documented inline.
You can generate full docs by running doxygen in the root directory it might help when navigating the internals.

Also, if you have any thoughts or suggestions on the overall architecture, I’d genuinely love to hear them.
I tried to keep things simple and minimal, but I’ll admit I don’t have a fully solid mental model of the architecture yet and I may have messed things up in a few places. If there’s a better structural direction, I’m all ears.

That said, I really believe this project has potential and that’s why I’m excited to keep improving it.
Your insights so far have already been super valuable, and I appreciate every bit of input.

Thanks again for all your time and support!