Impressed by Microsoft’s compiler toolchain having a “std:c++newest” choice for robotically focusing on the newest supported C++ spec, GCC compiler builders have been discussing the potential for an identical function with the power to specify -std=c++present for the present C++ commonplace or -std=c++future for the longer term/draft specification.
The concept is to have GCC help “-std=c++present” that might be a transferring goal to the present C++ specification supported by the compiler whereas “-std=c++future” could be for focusing on the present work-in-progress/draft C++ specification in present working kind. There would even be comparable gnu++present / gnu++future choices for the GNU C++ prolonged variants.
Whereas the concept is good, in apply some considerations have already been raised over this being a continuing transferring goal and will result in person confusion. Particularly, with builders/customers usually operating a compiler that may be a yr or a number of years previous, the “present” and “future” targets will imply totally different C++ variations and never essentially what is definitely the present/future goal on the time of use. Particularly on enterprise Linux distributions the place customers out-of-the-box may be operating a a number of yr previous compiler, decoding the which means of present/future won’t essentially be correct with what the person is anticipating.
For now the proposed GCC choices are being mentioned in this gcc-patches mailing list thread for these within the prospects of -std=c++present and -std=c++future.
