search for: property3

...ll map nicely to the concept of "composite primary keys" which has a clean solution that I like[1], and could be used as inspiration. Or even something as simple as: template<typename Visitor> void visit(Visitor & v) { v.keys("Property1","Property2","Property3"); } I have never done this, but I expect we could also use constexpr to unroll many things at compile-time. That could be fun! Backward compatibility for serialization is also achievable using a method very similar to Boost serialization[2]: template<typename Visitor> void visit(Visi...

...e concept of "composite primary keys" which has a clean solution that I like[1], and could be used as inspiration. Or even something as simple as: > > template<typename Visitor> > void visit(Visitor & v) { > v.keys("Property1","Property2","Property3"); > } > > I have never done this, but I expect we could also use constexpr to unroll many things at compile-time. That could be fun! > > Backward compatibility for serialization is also achievable using a method very similar to Boost serialization[2]: > > template<t...

> On May 29, 2018, at 12:55, Adrian Prantl <aprantl at apple.com> wrote: > > > >> On May 29, 2018, at 12:28 PM, David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> wrote: >> >> +some of the debug info cabal (& Duncan, as an emeritus member, and person who plumbed a lot of the current debug info syntax support in) >>

> On May 29, 2018, at 12:28 PM, David Blaikie <dblaikie at gmail.com> wrote: > > +some of the debug info cabal (& Duncan, as an emeritus member, and person who plumbed a lot of the current debug info syntax support in) > > Visitor seems plausible though I haven't looked at the code in detail to see if it'd work perfectly. > > On Tue, May 29, 2018 at 7:56