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 2002:a37:7d43:: with SMTP id y64mr2003835qkc.168.1569326545199;
        Tue, 24 Sep 2019 05:02:25 -0700 (PDT)
X-Received: by 2002:a9d:744d:: with SMTP id p13mr1429864otk.76.1569326544842;
 Tue, 24 Sep 2019 05:02:24 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!o24no4402316qtl.0!news-out.google.com!q23ni263qtl.1!nntp.google.com!o24no4402310qtl.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 24 Sep 2019 05:02:24 -0700 (PDT)
In-Reply-To: <cc19a301-1198-4213-b746-ae2bc1078be8@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2.123.139.67;
 posting-account=L2-UcQkAAAAfd_BqbeNHs3XeM0jTXloS
NNTP-Posting-Host: 2.123.139.67
References: <ea369318-97cb-434f-9ba1-844d83db5f61@googlegroups.com>
 <cc19a301-1198-4213-b746-ae2bc1078be8@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5edf39fb-169a-463a-b28e-ece1d3b553e0@googlegroups.com>
Subject: Re: Implementing Rust's borrow checked pointers
From: Lucretia <laguest9000@googlemail.com>
Injection-Date: Tue, 24 Sep 2019 12:02:25 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader01.eternal-september.org comp.lang.ada:57180
Date: 2019-09-24T05:02:24-07:00
List-Id: <comp.lang.ada>

On Tuesday, 24 September 2019 12:23:30 UTC+1, Optikos  wrote:

> > begin
> >    A.all ... ; -- raises exception.
> 
> No, to be as useful as Rust's borrow checker, instead of raising exception, it needs to be a compile-time error.  The compiler needs to maintain a whole-program directed graph at compile-time, not defer a detection-based localized analysis to run-time.

Yes, the compiler would raise that exception at compile time. This idea that all exceptions are raised at runtime is false and you should check the AARM.