DIP60: @nogc attribute

[Walter Bright via Digitalmars-d]

On 4/22/2014 11:28 AM, Steven Schveighoffer wrote:
> On Tue, 22 Apr 2014 14:12:17 -0400, Walter Bright <newshound2 at digitalmars.com>
> wrote:
>
>> On 4/22/2014 6:18 AM, Steven Schveighoffer wrote:
>>> On Mon, 21 Apr 2014 19:02:53 -0400, Walter Bright <newshound2 at digitalmars.com>
>>> wrote:
>>>> The thing is, with iOS ARC, it cannot be statically guaranteed to be memory
>>>> safe.
>>>
>>> So?
>>
>> If you see no value in static guarantees of memory safety, then what can I say?
>
> Seriously, the straw man arguments have to stop.
>
> There is plenty of valuable D code that is not guaranteed memory safe.

Memory safety is not a strawman. It's a critical feature for a modern language, 
and will become ever more important.


 > For example, druntime.

Nobody expects a GC's guts to be guaranteed memory safe. But they do expect the 
interface to it to be memory safe, and using GC allocated data to be memory 
safe, and being able to write performant memory safe code.

And by memory safe, I don't mean hand verified. I mean machine verified.