Tail pad optimization, cache friendlyness and C++ interrop

[Walter Bright via Digitalmars-d]

On 6/15/2014 2:30 AM, Maxim Fomin wrote:
> On Wednesday, 11 June 2014 at 16:50:30 UTC, Walter Bright wrote:
>> On 6/11/2014 4:34 AM, Timon Gehr wrote:
>>> Not memory safe implies (is supposed to imply) not @safe but not @safe does not
>>> imply not memory safe.
>>
>> @safe in D == memory safe.
>
> Why? I found dozens of cases when @safe is broken, let alone other issues in
> bugzilla.

Those are bugs. We aim to fix them.


> By the way, memory safety is also compromised by compiler bugs which make him
> generate buggy code. Note, when I counted memory safety problems, codegen issues
> were not counted.

I don't think we should mix intention with bugs. Bugs need to get fixed.


> I have reached this conclusion some years ago and nothing has change in D since
> then which make me reconsidering my opinion (including that @safe holes were not
> fixed).

I do welcome help in fixing bugs.