> From: Neal Gompa <n...@gompa.dev> > Date: Wed, 10 May 2023 08:10:48 -0400 > Cc: s...@gentoo.org, eg...@gwmail.gwu.edu, jwakely....@gmail.com, > j...@rtems.org, dje....@gmail.com, ja...@redhat.com, ar...@aarsen.me, > gcc@gcc.gnu.org, c-std-port...@lists.linux.dev > > On Wed, May 10, 2023 at 8:05 AM Eli Zaretskii <e...@gnu.org> wrote: > > > > > From: Neal Gompa <n...@gompa.dev> > > > Date: Wed, 10 May 2023 06:56:32 -0400 > > > Cc: Eric Gallager <eg...@gwmail.gwu.edu>, Jonathan Wakely > > > <jwakely....@gmail.com>, j...@rtems.org, > > > David Edelsohn <dje....@gmail.com>, Eli Zaretskii <e...@gnu.org>, > > > Jakub Jelinek <ja...@redhat.com>, > > > Arsen Arsenović <ar...@aarsen.me>, gcc@gcc.gnu.org, > > > c-std-port...@lists.linux.dev > > > > > > Right, we've been going through a similar effort with C++ over the > > > past decade. GCC incrementally becoming more strict on C++ has been an > > > incredibly painful experience, and it eats away a ton of time that I > > > would have spent dealing with other problems. Having one big event > > > where the majority of changes to make the C compiler strict happen > > > will honestly make it less painful, even if it doesn't seem like it at > > > the moment. > > > > But not having such an event, ever, would be even less painful. > > That's not going to happen.
Well, I hope it will. Otherwise I wouldn't be partaking in this discussion.
