Feedback on proposal for #ReflectiveAccessToNonExportedTypes

[Alan Bateman]

On 08/07/2016 09:39, Sander Mak wrote:
> That is, define your module-info's, possibly containing dynamic exports if your framework of choice does its magic through reflection.
>
Right and there is nothing in this proposal that is specific to core 
reflection either. The framework that I am using might be spinning 
bytecode or maybe it switches to using method handles when there is a 
waning gibbous moon - that's implementation detail that the user of the 
framework should be oblivious too.

-Alan