Review request 8153895 (proxy) redundant read edges to superinterfaces of proxy interfaces
peter.levart at gmail.com
Tue Apr 12 14:18:53 UTC 2016
On 04/12/2016 03:16 PM, Peter Levart wrote:
> The problem is of course with the setup procedure of the dynamic
> module where you have to add exports from modules/packages of those
> referenced types and read edges to modules of those references types
> upfront. But this problem is resolvable. If a type is not visible from
> the proxy class' class loader, then we don't need an export from its
> module/package and we don't need a read edge to its module, do we?
> What do you think?
If you think my claims make sense, then the following change could
establish such policy:
More information about the core-libs-dev