On Saturday, 30 November 2013 at 08:42:11 UTC, Iain Buclaw wrote:
But how do you expect this to be implemented? Implicitly putting GC.disable/GC.enable at the prologue / epilogue of a function?
The purpose of @nogc is not to prevent the GC from running when you make an allocation, it's to have compile-time assurance that the function (and any other functions it calls) won't set off any GC allocations in the first place. It should work the same way as @nothrow which guarantees a function won't throw an exception.
