https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> --- > Am 25.05.2023 um 20:24 schrieb pinskia at gcc dot gnu.org > <gcc-bugzi...@gcc.gnu.org>: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801 > > --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- > (In reply to Scott Zhong from comment #4) >> The move constructor "steals" resources rather than make copies of them, and >> leave the argument in some valid but otherwise indeterminate state. It is >> reasonable that size_ is not initialized in the context of a move >> constructor. Maybe, but you still copy an uninitialized variable so the diagnostic is correct.
