On Saturday, 4 January 2014 at 04:20:30 UTC, David Nadlinger
wrote:
This is not true. While it _is_ possible to get null pointers
in @safe code, they are not a safety problem, as the first page
is never mapped in any D processes (yes, I'm aware of the
subtle issues w.r.t. object size here, c.f. Bugzilla). And if
you find a way to obtain a dangling pointer in @safe code,
please report it to the bug tracker, this is not supposed to
happen.
What happens when you have an object/array/struct/whatever that
is larger than a page, and access one of the members/indices that
is more than one page-size away from the starting point? Wouldn't
this cause memory corrupting if the second page is mapped and you
have a NULL pointer?
