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

On 4/12/2012 7:37 PM, Jeffrey Lee Hellrung, Jr. wrote:

compiler?

Clang on Apple, not sure of the version other than that I don't think it's the very latest.

Try

return boost::move(future_result);

No, I actually had to replace boost::move with std::move to compile on VS10 (which has std::move) and Boost 1.47 (which doesn't have boost::move it seems. Introduced in 1.48?) —John