https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116178
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- I don't like the idea of adding -std=c++current to mean an unstable, experimental release. c++current sounds too inviting and safe, but our C++23 support (the current standard) is nowhere near complete, and even the C++20 library isn't stable yet. I would be happier with -std=c++experimental or possibly -std=c++next