On 13 September 2018 at 10:38, Ville Voutilainen <ville.voutilai...@gmail.com> wrote: > Howdy! The tricky details of copy constructors, part 76. > In this approach, I let the const-copy "dominate"; that is, if > a const-copy was found, a non-const-copy will not turn off triviality > of the copy constructor, and a const-copy will reinstate triviality > of the copy constructor even if a non-const copy removed said > triviality.
Curses.. the resetting is over-eager; we might have a non-trivial base or a member, and in those cases we shouldn't reset the triviality when we see a non-user-provided const copy. I think I'll hack around this with a non 0/1 value. :)
