A different way to use boost serialization
summary
Tree nodes hold boost::variant types and serialization is moved out of headers by returning a tie-like tuple of member references and serializing it with boost::fusion::for_each, so concrete types serialize without intrusive header methods or public members. A macro generates the tuple accessor per class, and the heavy serialization glue lives in a .cpp (serialization in CPP), avoiding full recompiles. It works on the demo model and derived-type handling is macro-supported, though the macro-heavy approach feels inelegant and may hurt performance.
AI-written summary · about
chapters (4)
related talks
42mSerialization in C++ has never been easier! But wait, there's more
57mAdventures in Serialization: A Flexible Approach for Embedded Systems in C++
01h 02mBinary Object Serialization With Structure Traversal & Reconstruction
03mstd::variant & Blockchain
50mType safe C++? LOL!
01h 34mMetaprogramming in C++14
01h 13mType safe C++ – LOL! :-)
03mLet's cmakeify the C++ standard library