I don't think this is intended rather it appears to be a bug/deficiency in the constructor flow analysis of DMD, which from what I'm reading is very rudimentary.
If I'm using a delegate in B, supplied to super() and called in A, then it works :P
Re: Constructor called instead of opAssign()
frame via Digitalmars-d-learn Tue, 16 Feb 2021 03:05:37 -0800
On Tuesday, 16 February 2021 at 09:04:43 UTC, Boris Carvajal
wrote:
- Constructor called instead of opAss... frame via Digitalmars-d-learn
- Re: Constructor called instead... Boris Carvajal via Digitalmars-d-learn
- Re: Constructor called ins... frame via Digitalmars-d-learn
- Re: Constructor called... Boris Carvajal via Digitalmars-d-learn
- Re: Constructor ca... frame via Digitalmars-d-learn
