From: "Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>
Subject: Re: Implementing Rust's borrow checked pointers
Date: Tue, 24 Sep 2019 18:24:21 +0200
Date: 2019-09-24T18:24:21+02:00 [thread overview]
Message-ID: <qmdfvn$oam$1@dont-email.me> (raw)
In-Reply-To: <ea369318-97cb-434f-9ba1-844d83db5f61@googlegroups.com>
On 9/24/19 11:05 AM, Lucretia wrote:
>
> type P is restricted access X;
>
> Restricted in this case would mean that once assigned it cannot be re-assigned into or out of with out some sort of move operation, which could be implemented as an attribute on the access type.
What's wrong with "limited"?
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.
--
Jeff Carter
"Drown in a vat of whiskey. Death, where is thy sting?"
Never Give a Sucker an Even Break
106
next prev parent reply other threads:[~2019-09-24 16:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 9:05 Implementing Rust's borrow checked pointers Lucretia
2019-09-24 9:57 ` Dmitry A. Kazakov
2019-09-24 11:23 ` Optikos
2019-09-24 12:02 ` Lucretia
2019-09-24 14:08 ` Optikos
2019-09-24 18:56 ` Simon Wright
2019-09-24 19:13 ` Keith Thompson
2019-09-24 20:15 ` Optikos
2019-09-24 20:31 ` Keith Thompson
2019-09-24 20:40 ` Optikos
2019-09-24 20:53 ` Keith Thompson
2019-09-24 22:09 ` Lucretia
2019-09-24 22:24 ` Keith Thompson
2019-09-25 4:36 ` J-P. Rosen
2019-09-25 15:04 ` Simon Wright
2019-09-24 12:23 ` Lucretia
2019-09-25 17:21 ` Stephen Leake
2019-09-24 16:24 ` Jeffrey R. Carter [this message]
2019-09-25 16:26 ` Florian Weimer
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox