DIP60: @nogc attribute

[Walter Bright via Digitalmars-d]

On 4/17/2014 9:42 AM, monarch_dodra wrote:
> That said, your proposal could be applied for all attributes in general. Not
> just @nogc in particular. In practice though, a simple unittest should cover all
> your needs. simply create a @nogc (pure, nothrow, safe, ctfe-able) unitest, and
> call it with a trivial argument. If it doesn't pass, then it probably means you
> made a gc-related (or impure, throwing, unsafe) call that's unrelated to the
> passed parameters.

Yup, that should work fine.