On Fri, 2012-11-16 at 23:45 +0100, Rob T wrote: > This should be a compiler error or at the very least issue a > warning. > > It seems to me that overridden sub-struct opAssign needs to be > chained together, and it's a compiler error if there's a break in > the chain, i.e., if a sub-level struct has non-default opAssign, > then the parent must have one too, else it's an error. >
The default generated should simply call the user specified ones of any sub struct. Where can I find this bug? When searching for opAssign I can't find it. I would like to vote for it.
