The "@safe vs struct destructor" dilemma
Kagamin
spam at here.lot
Sat Apr 12 06:05:20 PDT 2014
On Saturday, 12 April 2014 at 11:06:33 UTC, Michel Fortin wrote:
> Well, that's a general problem of @safe when dereferencing any
> potentially null pointer. I think Walter's solution was to
> insert a runtime check if the offset is going to be beyond a
> certain size.
Well, if you don't access anything beyond a certain offset, it
doesn't make sense to declare something that large. So, it would
be a compile-time check, not run-time.
More information about the Digitalmars-d
mailing list