On terça-feira, 5 de novembro de 2013 18:10:30, Marc Mutz wrote: > Any integer type would previously pick the (int) ctor. Now, everything > except int and qint64 will be ambiguous, in particular unsigned int. > > Hmm, or maybe the (bool) overload already made everything other than int > and bool ambiguous?
Wasn't it ambiguous with that double too?
$ g++ -xc++ -fsyntax-only - <<<'void f(int); void f(double); void g() { f(1u);
}'
<stdin>: In function ‘void g()’:
<stdin>:1:45: error: call of overloaded ‘f(unsigned int)’ is ambiguous
<stdin>:1:45: note: candidates are:
<stdin>:1:6: note: void f(int)
<stdin>:1:19: note: void f(double)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
