Please review the " temporary storage class specifiers" and "C++ is the next C++" attachment. It could be the avenue of making some of these changes in the language. It is an example of changing one of C++ defaults. It provides the means to have the change now for those who need and want it and a path for those who can't to migrate over to the new default.

On Wed, Sep 28, 2022 at 11:27 AM Phil Bouchard via Std-Proposals <> wrote:

On 9/28/22 11:08, Jason McKesson wrote:

The goal here is to extend the language, on its architectural scale, to fix somehow these long lasting issues in C++. No matter how long it can take, they have to be fixed.
Your goal is not really relevant at this point. The mechanism you are
proposing is one that is, by definition, outside of the language.

The C++ standard does not define a "compiler", "architecture",
tool-set or anything like that. It defines what the language means.
How that gets processed into an executable is not what the standard

The committee can issue guidance about how implementers should go
about writing implementations. But that's not part of the language
standard. What you want is an extra-language tool. That is simply not
in the purview of the standard.

Ok so by "definition" there is no hope of extending the C++ language itself other than creating a new variant. Ok thanks I understand.

Phil Bouchard facebook icon
T: (819) 328-4743
E: |
1188 rue Saint-Louis | Gatineau (Qc), J8T 2L8 Canada
Banner Le message ci-dessus, ainsi que les documents l'accompagnant, sont destinés uniquement aux personnes identifiées et peuvent contenir des informations privilégiées, confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce message par erreur, veuillez le détruire.
This communication (and/or the attachments) is intended for named recipients only and may contain privileged or confidential information which is not to be disclosed. If you received this communication by mistake please destroy all copies.
Std-Proposals mailing list