On Wednesday, 16 April 2014 at 08:46:56 UTC, Ola Fosheim Grøstad
wrote:
On Tuesday, 15 April 2014 at 23:54:24 UTC, Matej Nanut via
Digitalmars-d wrote:
This shouldn't be a problem if you plonk @nogc: at the top of
your own file, as it won't compile anymore if you try to call
@gc functions.
It is a problem if you are allowed to override @nogc with @gc,
which is what the post I responded to suggested.
Btw, I think you should add @noalloc also which prevents both new
and malloc. It would be useful for real time callbacks, interrupt
handlers etc.
