On 28/05/17 22:13 +0200, François Dumont wrote:
Sure but like freedom which stop where start others' freedom so does those requirements :-). Because the Standard says that an allocator will be value-init when there is no default-init it makes usage of the C++11 default constructor more complicated.
It makes the std::lib implementors job harder, for the benefit of users. That is the correct trade off. We don't get to ignore the guarantees of the standard just because they're difficult.
