(Coming back to this patch and ready to push this change later today)

Here is the updated webrev:
   http://cr.openjdk.java.net/~mchung/jdk14/8173978/webrev.02/

This includes the change that Peter suggested accepting m2 == null.


Mandy

On 7/5/19 12:29 PM, Peter Levart wrote:
Hi Mandy,

Yes, either way will avoid double canRead/isExported calls against the same module. Although perhaps, an API with null prevModule would be more consistent with other API methods that use null prevLookupClass etc...

Regards, Peter

Reply via email to