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!.POSTED!not-for-mail
From: "Alejandro R. Mosteo" <alejandro@mosteo.com>
Newsgroups: comp.lang.ada
Subject: Re: Microsoft is considering moving to Rust; potential opportunity
 for Ada2020
Date: Wed, 7 Aug 2019 11:09:05 +0200
Organization: A noiseless patient Spider
Message-ID: <qie4fh$t00$2@dont-email.me>
References: <01e1fc91-a20e-4b48-a10e-57d3935cd06c@googlegroups.com>
 <b9528bc1-55e0-4de6-b255-f13e55a0680c@googlegroups.com>
 <0d4e46d4-c227-4d7a-aafa-44492c6e1d41@googlegroups.com>
 <871ryop74h.fsf@nightsong.com> <ly5znx7k6u.fsf@pushface.org>
 <qicboo$e34$1@dont-email.me>
 <f8a1dfaa-c36a-4a66-b8fd-873888091ed3@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 7 Aug 2019 09:09:05 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
 posting-host="80dd61ee4a2de23f9405af3c5030bdfa";
	logging-data="29696"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18tk61JjBdGOgNVqiD0hMLT"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
Cancel-Lock: sha1:33eDshyRv6UwCpd2QbVRFljnTN0=
In-Reply-To: <f8a1dfaa-c36a-4a66-b8fd-873888091ed3@googlegroups.com>
Content-Language: en-US
Xref: reader01.eternal-september.org comp.lang.ada:57005
Date: 2019-08-07T11:09:05+02:00
List-Id: <comp.lang.ada>

On 6/8/19 19:49, Brad Moore wrote:

> I believe it is also not just related to concurrency. For example, if you pass a pointer to an object into a function which deletes the object, the compiler will detect that use of that pointer after calling the function is not allowed.

Yes; concurrency safety (in a limited sense) is the side-effect, not the 
main point, I'd say.