[core-libs] RFR (L): 8010319: Implementation of JEP 181: Nest-Based Access Control (original) (raw)
Peter Levart peter.levart at gmail.com
Mon May 21 06:12:26 UTC 2018
- Previous message: [core-libs] RFR (L): 8010319: Implementation of JEP 181: Nest-Based Access Control
- Next message: [core-libs] RFR (L): 8010319: Implementation of JEP 181: Nest-Based Access Control
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 05/21/2018 07:57 AM, David Holmes wrote:
Do we really need to spell out the case for primitives and arrays? If so would it suffice to add the following:
"A class or interface that is not explicitly a member of a nest *(such as primitive or array classes)*, is a member of the nest consisting only of itself, and is the nest host. Every class and interface is a member of exactly one nest."
That's fine, but then someone might wonder whether only primitive and array classes are not explicit members of a nest.
What about:
"A class or interface that is not explicitly a member of a nest (including but not limited to primitive and array classes), is a member of the nest consisting only of itself, and is the nest host. Every class and interface is a member of exactly one nest."
Regards, Peter
- Previous message: [core-libs] RFR (L): 8010319: Implementation of JEP 181: Nest-Based Access Control
- Next message: [core-libs] RFR (L): 8010319: Implementation of JEP 181: Nest-Based Access Control
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]