Fix std::pair std::is_copy_assignable behavior
Wed Apr 17 19:43:00 GMT 2013
On 04/17/2013 09:18 PM, Paolo Carlini wrote:
> On 4/17/13 8:10 PM, FranÃ§ois Dumont wrote:
>> Here is an other proposal to fix
> Sorry, I'm still missing something very, very basic: which behavior is
> conforming, the current one or what we would get instead? If the
> former, is there a DR arguing for the latter?
The behavior I am targeting is
std::is_copy_asignable<std::pair<const int, int>> to be std::false_type
for instance. I have added test for many other use cases. More generally
I need that when std::is_copy_assignable<T> is std::true_type then
writing a = b, with a and b being T, does compile.
Otherwise this patch just make std::pair match the Standard
requirements like at 220.127.116.11. Do you want me to add a bug report in
Bugzilla first ?
More information about the Libstdc++