--- Comment #2 from Jonathan M Davis <> 2012-10-17 16:35:57 
PDT ---
> This is a big change in D, so before going this route I suggest to think well
about this topic.

The thing is that it _isn't_ memory safe. There's no question of that. So, per
the definition of @safe, it has no business being @safe. It needs to be
@system. If it's not, then SafeD is broken. I don't see how anyone could argue

Yes, it's breaking change in the cases where people actually use @safe, but
there's no way around that, and honestly, I suspect that most people don't mark
their code @safe anyway, and it's only applicable to where static arrays are
sliced, so I don't know how much code will really be broken. For folks who use
static arrays and @safe heavily, it'll break a lot. For most other people,
probably nothing.

Regardless, I don't see how we can _not_ make this change given what @safe is
supposed to do.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to