Re: Storing noncopyable but movable object in std::function

Daniel Kr?gler wrote:


I thought those static deduction tools were fairly unreliable to begin
with. I just checked on this simple example that a pair of move-only
types is reported as copy-assignable by g++, which blindly follows
the standard definition of std::pair. Actually assigning will result
in a compile-time error and not a runtime one though.

#include <utility>
#include <iostream>
#include <iomanip>
#include <type_traits>
struct A {
       A(){}
       A(A const&)=delete;
       A(A &&){}
};
int main(){
       std::cout << std::boolalpha;
       std::cout << std::is_copy_assignable<std::pair<A,A> >::value << '\n';
       std::pair<A,A> a,b;
       // b=a;
}

--
      [ See http://www.gotw.ca/resources/clcm.htm for info about ]
      [ comp.lang.c++.moderated. First time posters: Do this! ]