Bug 23946 – specifications state that "there can only be one destructor" which can be confusing because of mixin templates

§2 of https://dlang.org/spec/class.html#destructors states that "There can be only one destructor per class, the destructor does not have any parameters, and has no attributes. It is always virtual." However this creates confusion as mixin templates are allowed to introduce a destructor. eg. ``` import std; mixin template AddNewDtor() { ~this() { writeln("Mixin dtor"); } } class Foo { ~this() { writeln("Class dtor"); } mixin AddNewDtor; } void main() { { auto s = scoped!Foo; // prints `Mixin dtor` // prints `Class dtor` } } ``` The specifications should be more clear. While some might know that there are the internal __dtor and __xdtor functions, the specs should mention that "destructors introduced by mixin templates are implicitly called by the main destructor and does not represent a real destructor" in https://dlang.org/spec/template-mixin.html. That's just a suggestion, any other solution that would prevent a possible confusion for new comers is welcome. See NG thread : https://forum.dlang.org/post/[email protected]

@ntrel created dlang/dlang.org pull request #3636 "Fix Issue 23946 - spec states "there can only be one destructor"" fixing this issue: - Fix Issue 23946 - specifications state that "there can only be one destructor" ...which can be confusing because of mixin templates https://github.com/dlang/dlang.org/pull/3636

dlang/dlang.org pull request #3636 "Fix Issue 23946 - spec states "there can only be one destructor"" was merged into master: - b70588595470372436c3f9b10ed91cb2cd3dc635 by Nick Treleaven: Fix Issue 23946 - specifications state that "there can only be one destructor" ...which can be confusing because of mixin templates https://github.com/dlang/dlang.org/pull/3636