Re: Visibility of Indexing aspects

[Jere <jhb.chat@gmail.com>]

On Saturday, July 14, 2018 at 7:00:36 PM UTC-4, Shark8 wrote:
> On Saturday, July 14, 2018 at 12:29:44 PM UTC-6, Jere wrote:
> > 
> > There was no mention of being able to index the type (publicly), so it
> > surprised me that a client using the package could call the index
> > operation.  If it was intentional, then that was fine, I just wanted to
> > know because I couldn't find anything in the RM that forbid it, but I 
> > might have missed something.
> 
> You do raise a good point though WRT to visibility; it *would* be more consistent with Ada to have a distinction between (eg) publicly indexable and privately indexable types based on where the aspects lay.
> 
> OTOH, certain aspects such as (eg) Convention don't need to be public to alter the type in some manner. (Analogous to putting [eg] PRAGMA CONVENTION(FORTRAN, MATRIX) to force the Matrix to be represented in a Column-major manner within the private part.)
> 
> I should write this up as an AI for the ARG, if for nothing else than clarification's sake. Thank you for bringing the issue to my attention.

Thanks!
One positive thing about it is that it does allow for safer indexing.
Normally you have to expose a reference type with Implicit_Dereference, 
which exposes access types to your interface and also increases 
design complexity because you may have to figure out how to handle
those reference types potentially outliving the container.  Even though
the issue I raised feels inconsistent, in some ways it might be safer
than the standard way the containers handle indexing because the
reference type is now private and a user cannot save it to a variable
for later use.