Re: Implementing Rust's borrow checked pointers

[Keith Thompson <kst-u@mib.org>]

Optikos <optikos@verizon.net> writes:
> On Tuesday, September 24, 2019 at 3:31:15 PM UTC-5, Keith Thompson wrote:
[...]
>> Again, the claim (from Lucretia, not from you) was:
>> 
>>     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.
>
> I already answered that in my 9:08AM reply today.  I demonstrated via
> extensive quotation from AARM that Luke utilized the incorrect
> term-of-art.  According to the AARM as written, Luke meant “error” (as
> quoted from AARM) when he wrote “exception” (as quoted from c.l.a).
> With a relatively minor change from Luke's “raise exception” to emit
> error message at compile-time, Luke's statement is otherwise correct.
>
>> Printing a warning message is not raising an exception.

Ah, so you're agreeing with me.

I asked Lucretia to support the assertion that exceptions can be
raised during compilation.  I'm not sure your response was helpful.
I'd be interested in seeing a response *from Lucretia*. (Yes,
this is a public newsgroup and anyone can reply to anything, but
my question was intended to be directed to Lucretia.)

I think Lucretia simply made a mistake, but given the apparent
strength of the assertion I'd like to see a clarification.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */