dsimcha wrote:
== Quote from Travis Boucher ([email protected])'s article
Sean Kelly wrote:
 Its harder
to create a memory leak in D then it is to prevent one in C.

void doStuff() {
    uint[] foo = new uint[100_000_000];
}

void main() {
    while(true) {
        doStuff();
    }
}


Hmm, that seems like that should be an implementation bug. Shouldn't foo be marked for GC once it scope? (I have never used new on a primitive type, so I don't know)

Reply via email to