forcing "@nogc" on class destructors
ketmar via Digitalmars-d
digitalmars-d at puremagic.com
Tue Jan 20 13:47:25 PST 2015
On Tue, 20 Jan 2015 21:37:54 +0000
via Digitalmars-d <digitalmars-d at puremagic.com> wrote:
> On Tuesday, 20 January 2015 at 21:29:40 UTC, Steven Schveighoffer
> wrote:
> > How's that? The current runtime aborts on memory allocation
> > inside the GC collection routine, it's not a memory safety
> > issue.
>
> Spurious race conditions in memory deallocation patterns that
> remain undetected and cause random crashes after deployment are
> ok? That is not memory safety, it is "memory safety".
>
> The language should prevent this.
and the funniest thing that it is perfectly able to do that! all the
code is already there.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20150120/d9ffb96f/attachment.sig>
More information about the Digitalmars-d
mailing list