From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.36.41.74 with SMTP id p71mr2421144itp.11.1512071022886;
        Thu, 30 Nov 2017 11:43:42 -0800 (PST)
X-Received: by 10.157.85.67 with SMTP id h3mr201951oti.10.1512071022819; Thu,
 30 Nov 2017 11:43:42 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.kjsl.com!usenet.stanford.edu!i6no96491itb.0!news-out.google.com!x87ni92ita.0!nntp.google.com!193no94001itr.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 30 Nov 2017 11:43:42 -0800 (PST)
In-Reply-To: <ovpmb7$o7j$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=155.148.6.150;
 posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
NNTP-Posting-Host: 155.148.6.150
References: <d8c0ce45-97ad-4475-b3f9-1662a875a576@googlegroups.com>
 <e3a1f97e-7cbd-4327-aef6-c18ca9e74bc2@googlegroups.com>
 <ovidu5$eip$1@franka.jacob-sparre.dk>
 <ac428886-d567-4692-b8b7-22fcb69a755f@googlegroups.com>
 <0b6bd27e-e9ec-4854-bbb1-85e1d9ac92e1@googlegroups.com>
 <227d5a7f-6d5b-4b76-ac31-7d15bb6dc284@googlegroups.com>
 <ovn6uq$rdm$1@franka.jacob-sparre.dk>
 <16c980c2-1fa6-4084-97ea-b576c75b99c3@googlegroups.com>
 <3ca6a682-9af1-40e3-a4ac-db739b38e4d7@googlegroups.com>
 <8a31c728-0261-4f41-b82e-e7128369ebc1@googlegroups.com>
 <f8ak08F916jU1@mid.individual.net>
 <6c5efd03-6dfe-4024-9c28-b4460006ed39@googlegroups.com>
 <ovpmb7$o7j$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ed357f21-d318-4768-a756-b86e9532a1ae@googlegroups.com>
Subject: Re: How to access an array using two different indexing schemes
From: Shark8 <onewingedshark@gmail.com>
Injection-Date: Thu, 30 Nov 2017 19:43:42 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:49278
Date: 2017-11-30T11:43:42-08:00
List-Id: <comp.lang.ada>

On Thursday, November 30, 2017 at 12:31:53 PM UTC-7, G. B. wrote:
> AdaMagica wrote:
> > Am Donnerstag, 30. November 2017 15:47:40 UTC+1 schrieb Niklas Holsti:
> >> Perhaps the next Ada revision could extend 4.6(5/2) to include a type=
=20
> >> conversion in a renaming, as a view conversion?
> >=20
> > I sent this request to Ada Comment.
> >=20
>=20
> Isn=E2=80=98t a type conversion potentially copying?

Perhaps, but a renaming [of extant data] shouldn't be... Especially in this=
 particular case since we have bounds-sliding anyways.

What is wanted here is a View Conversion, not really a Type Conversion.