November 18, 2017 @nogcclass? (Way to solve bugs regarding destroy) | ||||
---|---|---|---|---|
| ||||
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. |
November 18, 2017 Re: @nogcclass? (Way to solve bugs regarding destroy) | ||||
---|---|---|---|---|
| ||||
Posted in reply to 12345swordy | On Saturday, 18 November 2017 at 20:06:28 UTC, 12345swordy wrote: > 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. That's known: https://issues.dlang.org/show_bug.cgi?id=17297. It cant be solved easily. Even the experiemental allocator `dispose()` function cant be @nogc. |
Copyright © 1999-2021 by the D Language Foundation