On Sunday, 24 June 2012 at 14:17:14 UTC, Alex Rønne Petersen
wrote:
Call me weird, but that seems like it would completely
undermine the @safe'ty system, no? Maybe I'm misunderstanding?
It just seems like that kind of escape hatch would result in
@safe meaning basically nothing...
@safe just means that somebody promised you that the piece of
code in question is memory safe – either the compiler by
disallowing pointer arithmetic, ..., or the implementor using
@trusted. We really shouldn't continue the discussion in this
thread, though.
David
