February 15, 2020 [Issue 20582] destroy should be @nogc if class destructor is @nogc | ||||
|---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=20582 Harry Vennik <htvennik@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|destroy should be @nogc if |destroy should be @nogc if |class constructor is @nogc |class destructor is @nogc -- | ||||
February 15, 2020 [Issue 20582] destroy should be @nogc if class destructor is @nogc | ||||
|---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=20582 moonlightsentinel@disroot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |moonlightsentinel@disroot.o | |rg Hardware|x86_64 |All Resolution|--- |DUPLICATE OS|Linux |All --- Comment #1 from moonlightsentinel@disroot.org --- This is effectively caused by the way destructor chaining is implemented using rt_finalize (which iterates all destructors using RTTI). This makes static type checking for chained destructors impossible right now. So even if the destructor of the current class is @nogc those found in the parent classes might not be - without checking. *** This issue has been marked as a duplicate of issue 15246 *** -- | ||||
Copyright © 1999-2021 by the D Language Foundation
Permalink
Reply