Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve looked at cppreference.com and they seem to indicate no noexcept specification on std::function(std::function&&). This seems rather odd to me. Does the standard really not give a nothrow guarantee in this case?
I imagine that the
functionobject is capable of storing an arbitrary, user-defined, callable object. When you move thefunctionobject, that contained, user-defined object is moved as well, and there are no guarantees that this can be done without exceptions.