This might sound cynical, but C++ reflection seems to never happen. What’s needed is perhaps a bare minimum that can be extended or even thrown away afterwards.
That’s better than wasting another few decades to find out the community can’t agree on C++ reflection, again
This is a proposal for a reduced initial set of features to support static reflection in C++.
That seems to be the committee policy these days - get the minimal version of a feature out of the gate first and then spend a decade extending it. Unfortunately sometimes they can’t even agree on what the bare minimum should be, which also causes the burn out of proposal authors and proposals get stalled (like what happened with reflection, though it seems that it’s in the works again).
Reflection and contracts would be really great if they make their way. But… maybe I have to wait 20 years just to get a minimal version that can be totally done with macros anyway…
Nah, I’m just kidding, but…