concept member function in category c++
appears as: member function, member functions, member function

This is an excerpt from Manning's book C++ Concurrency in Action, Second Edition.
This is much more descriptive than the original code and clearly expresses the intent. It also allows the compiler to give more descriptive error messages and moves the error from link time to compile time if you try to perform the copy within a member function of your class.
Effects Constructs copies of func and args... in internal storage (denoted by fff and xyz..., respectively). If policy is std::launch::async, runs INVOKE(fff,xyz...) on its own thread. The returned std::future will become ready when this thread is complete and will hold either the return value or the exception thrown by the function invocation. The destructor of the last future object associated with the asynchronous state of the returned std::future blocks until the future is ready. If policy is std::launch::deferred, fff and xyz... are stored in the returned std::future as a deferred function call. The first call to the wait() or get() member functions on a future that shares the same associated state will execute INVOKE (fff,xyz...) synchronously on the thread that called wait() or get(). The value returned or exception thrown by the execution of INVOKE(fff, xyz...) will be returned from a call to get() on that std::future. If policy is std::launch::async | std::launch::deferred or the policy argument is omitted, the behavior is as-if either std::launch::async or std:: launch::deferred had been specified. The implementation will choose the behavior on a call-by-call basis in order to take advantage of the available hardware concurrency without excessive oversubscription. In all cases, the std::async call returns immediately.