Oh great, the one way to make reflection even more unpredictable than it already is... So instead of "only" finding that my choice of method names, class struc

Oh great, the one way to make reflection even more unpredictable than it already is... So instead of "only" finding that my choice of method names, class structure and presence or absence of ostensibly unused class members can change programs behaviour in arbitrary ways, now that property will extend to the implementation code itself? Have fun getting reliable static analysis working on this stuff...