That would break a long tradition of shitty naming decisions inherited from C.

The proposal uses multiple inheritance in a few cases. I don’t know how it’s defined, though.

Does it work though? I can imagine one class having a rule restricting / correcting everything to be public, while the other restricts / corrects everything to be private or protected. Does second one look at the output of the first, or does it look at the use of $class definition.

Foreign keyboards often do have $, and you pretty much need it for programming anyway in a lot of environments.

$shell_or_perl_variable, /end_of_line_regex$/, and $.jquery_function() are all common examples, and I’m sure there are others I just can’t think of at the moment. I probably use $ for things not related to money than I actually use it for money.

Some don’t have ~ and & either to not speak about { and }

Lisp, it remembers me of CompuServe boards

Can you get the rest of the world to buy in? Foreign keyboards usually don’t have the $ sign. Or, is the capitalist Trump paying Sutter off?

Martin O’Riordan, who has been writing C++ compilers since 1986, told me at the weekend that something similar to metaclasses was proposed in the early 1990’s.

One of the first libraries to ship with CFront was a coroutines library. After 30 years this is finally becoming part of the standard. Such is the way of C++ standardisation.