On Nov 30, 2013 9:30 AM, "bearophile" <[email protected]> wrote: > > Iain Buclaw: > > >> But how do you expect this to be implemented? Implicitly putting >> GC.disable/GC.enable at the prologue / epilogue of a function? > > > The point of annotations like @nogc or @noheap is not to disable the GC, but to statically disallow its usage transitively inside a function. >
Ok, but what you describe is a different meaning to "no unexpected activity from the GC in critical sections". I'll have to double check, but do we still have a sort of global lock system in the GC for handling multiple threads? Regards -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';
