https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98639
Marek Polacek changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98639
--- Comment #5 from Arthur O'Dwyer ---
Meh, I guess this is just an unintended (but conforming) consequence of the
shifting C++17/20 rules. Jonathan links to
https://twitter.com/wakomeup/status/1274778577087627267 as another example:
// https://
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98639
Mathias Stearn changed:
What|Removed |Added
CC||redbeard0531 at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98639
--- Comment #3 from Jonathan Wakely ---
(In reply to Arthur O'Dwyer from comment #0)
> I actually suspect that this behavior is related to C++20's paren-init for
> aggregates;
Yes, and the change to allow aggregates to have base classes. Derived
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98639
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98639
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
