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

Subject: Re: [Boost-users] Problem with 'future' on compiler without move semantics
From: John M. Dlugosz (mpbecey7gu_at_[hidden])
Date: 2012-04-13 07:29:43

On 4/12/2012 7:40 PM, Jeffrey Lee Hellrung, Jr. wrote:
>
>     Try
>
>     return boost::move(future_result);
>
>
> Also, I'm pretty sure you'd need this regardless of the presence of (true) rvalue references.

Actually, I'm writing:

        #ifdef BOOST_NO_RVALUE_REFERENCES
         return future_result;  // built-in mover via implicit conversions
        #else
         return std::move(future_result);
        #endif

boost::move was not available with 1.47, but std::move must be if rvalue refs are available.

—John