Oh wait, you're C++ programmer. Of course, in that case your brain is already so horribly damaged that you can't perceive the comparatively mild benefits this would bring to a C++ programmer (removing only one cut from the thousand ones already killing you).
This is the problem with almost everyone who denigrates C++ and trys to hawk a better language. Their minds and outlook are simply too small and limited to see or understand the vast number of utterly different application domains spanned by C++.
You see reflection as a benefit because you work in a limited application area where reflection is useful (and where C++ would benefit). All those don't care types don't not care because they are brain damaged, they don't care because reflection would not have any benefit to them.
I do most of my coding around heavily algorithmic, scientific computing style stuff, with a side order of deep embedded. Reflection would not help me one bit day to day.
Yeah, I can see where it would be useful, but I don't write code in those areas, so it's quite low on my list of features I want.
But since I'm clearly so brain damaged, perhaps you'd like to enlighten me with what I should be using instead and why reflection would help me day to day.