Bug 18886 – Explicitly invoking super.__ctor in a constructor does not count as calling a super constructor

Example code at https://run.dlang.io/is/Is9tAs A workaround is to define a default constructor, as per https://run.dlang.io/is/mhM24Y But this is just doubling up on work that I shouldn't need to do. Came about because I was trying to explicitly invoke a templated constructor in a base class. Simple example at https://run.dlang.io/is/XAsoyo

This isn't a bug. Calling __ctor explicitly is advanced usage, not part of the usual typechecking. Is there any strong reason to keep this open? Is it preventing some use case?

The templated constructor use case looks valid, but the language doesn't allow you to explicitly call `super!(args)`...

Then we should allow that call.

yeah i agree.

errr and also while we're at it, perhaps calling `this!(args)` as well, for forwarding to another ctor in the same class.

The code I'm invoking in my current codebase extracts type data from the template parameter for object management. Another workaround would probably be to have a templated this( Type )( ref Type val ) in the base class and then call super( this ) from the derived class. Which feels as janky as it looks. Supporting super!( Args )() would be far more preferable, won't even need to do a __ctor hack then.

THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/17860 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB