https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116178
--- Comment #8 from Sam James <sjames at gcc dot gnu.org> --- Build systems like autoconf currently hardcode a list of C++ and C standards which has to be updated every so often (and often gets forgotten about). autoconf at least will aggressively pick the latest one it knows about. Obviously, it should be tested to make sure it works, but having to manually do "what's the latest I know about vs. latest the compiler knows about" feels cheesy. More so in C land, we also often see people doing things like "-std=gnu99" because at one point, that was new, and they don't mind using something newer, but then they have to try balance with whatever the latest the compiler supports. Being able to say "OK, try -std=latest-stable-std" is useful there. I think it's also likely to be useful in CI as people may not realise when their compiler starts to support a new standard (they may already know it exists and such but it's not yet in their Ubuntu image or whatever). The serious use cases I can think of are for 1) though, not the experimental stuff.
