On 16 April 2014 01:45, via Digitalmars-d <[email protected]> wrote: > Then you need a compiler option that will prevent @gc, otherwise you risk > libraries pulling in @gc code as quick fixes without library users that want > @nogc noticing the deficiency.
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.
