ATM the destroy function can't be called in a @nogc context, severely handicap the use of the @nogc attribute. Can we add a @nogcclass attribute for classes or at the very least have @nogc attribute apply stricter rules when applying to an entire class? Rules such as checking to see if every member variable and function is @nogc recursively until the base class that it's inherited from.

Reply via email to