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

Thiago Macieira thiago.macieira at intel.com
Fri Dec 25 13:24:03 CET 2015

On Friday 25 December 2015 10:35:02 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.

Except when they mean different things.

	auto v1 = QVector<int>{1, 2};
	auto v2 = QVector<int>(1, 2);

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list