Re: [Boost-users] Problem with 'future' on compiler without move semantics

Le 13/04/12 01:26, John M. Dlugosz a écrit :

In my earlier note, I figured it should just work. But it's not. I think it might be different on Boost 1.47?

Can anyone give me a VERY QUICK answer on how to return a unique_future on a compiler without && using Boost 1.47?

Can you try an undocumented function operator boost::detail::thread_move_t() { return boost::detail::thread_move_t(*this); } unique_future<int> bar() { return boost::detail::thread_move_t(foo())); } Please don't forget to post the exact example, the boost version, the compiler, ... HTH, Vicente