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
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.szaf.org!news.enyo.de!.POSTED!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Re: Implementing Rust's borrow checked pointers
Date: Wed, 25 Sep 2019 18:26:50 +0200
Message-ID: <87a7ass5o5.fsf@mid.deneb.enyo.de>
References: <ea369318-97cb-434f-9ba1-844d83db5f61@googlegroups.com>
	<qmdfvn$oam$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: news.enyo.de;
	logging-data="30014"; mail-complaints-to="news@enyo.de"
Cancel-Lock: sha1:WbKP6r0xkiXsikJjQ+cMjIPS+2A=
Xref: reader01.eternal-september.org comp.lang.ada:57194
Date: 2019-09-25T18:26:50+02:00
List-Id: <comp.lang.ada>

* Jeffrey R. Carter:

> There's already work on including something like Rust's borrow
> checking into Ada, but given how rarely access types are needed, and
> how easy it usually is to confine them to a restricted scope when
> they are, I don't see that it's worth the effort.

On the other hand, access types are not the only source of unsoundness
in Ada.  There is at least one other problem, involving records with
discriminants with defaults and aliasing.