C++11: string(50, 'x') versus string{50, 'x'}

Question

As seen on ideone:

cout << string(50, 'x'); // xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
cout << string{50, 'x'}; // 2x

WAT??

I have figured out that 50 is ASCII '2', so:

cout << static_cast<int>('2'); // 50
cout << static_cast<char>(50); // 2

But that's as far as I've got.

Does this lead to a solid argument against C++11 initializers?

the `initializer_list` constructor of `string` takes a list of characters, that's why. — The Paramagnetic Croissant, Nov 21 '14 at 14:40
([here's the relevant documentation.](http://en.cppreference.com/w/cpp/string/basic_string/basic_string)) — The Paramagnetic Croissant, Nov 21 '14 at 14:42
To answer the last line: No, it doesn't. It just means you have to understand what they do. — Cubic, Nov 21 '14 at 14:54

score 8 · Accepted Answer · answered Nov 21 '14 at 14:41

When you do string { 50, 'x' } you're essentially initializing the string with a list of characters.

On the other hand, string(50, 'x') calls a 2 argument constructor, which is defined to repeat the character x 50 times. The reason why string { 50, 'x' } doesn't pick the constructor is that it could be ambiguous. What if you had a three parameter constructor as well? If the type has an initializer_list constructor, it will be picked when you use { ... } for initialization.

Basically you need to be aware of the constructors your type has. The initializer_list constructor will always have a precedence to avoid ambiguity.

Shouldn't `{50, 'x'}` not be convertible to `std::initializer_list` due to the narrowing conversion? — Tavian Barnes, Dec 12 '14 at 22:39

C++11: string(50, 'x') versus string{50, 'x'}

1 Answers1

Linked