[Development] RFC: more liberal 'auto' rules?

Kevin Kofler kevin.kofler at chello.at
Sun Dec 27 02:17:00 CET 2015

Marc Mutz wrote:
> There are a lot of problems with the C declarator syntax (implicit
> narrowing conversions, hard-to-parse for humans, "most vexing parse",
> non-uniformity), and auto and uniform init and template aliases are the
> fixes. If you don't use them, then you're stuck in the C declarator
> syntax. You need to use a radically different syntax to get the nicer
> rules.

I consider the C declarator syntax just fine, it is very intuitive and has 
served us well for 26 years, so I don't see a need to change it.

Implicit narrowing conversions are a feature.

And what is hard to parse for humans? The "char* p,q" "issue"? That's a 
formatting bug then, this ought to be written "char *p, q", which makes it 
very clear what is going on.

        Kevin Kofler

More information about the Development mailing list