Re:Reflection for C++26
by bdd8f1df777b on Tuesday July 02, 2024 @10:05PM
(#40862169)
Without static reflection, we need to write a lot of boilerplate code, and those boilerplate is not guaranteed to stay in sync with the struct definition. That is why static reflection is sorely needed.
[ Parent
| on HN ]
Re:Reflection for C++26
by beached_whale on Wednesday July 03, 2024 @01:30AM
(#40862991)
Even static reflection isn’t a panacea and we have it now the libraries like PFR that give us a reference and name of each member for aggregates. But this is the same problem for anything else using those types too. For non-aggregates we need reflection or some manual library.
I am not disagreeing, just more saying what we have now.