Re: [Boost-users] Ambiguous boost::move

Subject: Re: [Boost-users] Ambiguous boost::move
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2011-12-13 18:18:25

Le 25/11/11 02:31, Kelvin Chung a écrit :
> I'm having this compiler issue while trying to use 
> boost::packaged_task (gcc, C++03, move emulation).  When I try to 
> compile, I get the following:
>
> src/KMBuilder.cpp:54: error: call of overloaded 
> ‘move(boost::unique_future<long unsigned int>&)’ is ambiguous
> boost/include/boost/thread/detail/move.hpp:44: note: candidates are: 
> typename boost::enable_if<boost::is_convertible<T&, 
> boost::detail::thread_move_t<T> >, boost::detail::thread_move_t<T>
>> ::type boost::move(T&) [with T = boost::unique_future<long unsigned 
> int>]
> boost/include/boost/move/move.hpp:294: note:                 typename 
> boost::move_detail::disable_if<boost::has_move_emulation_enabled<T>, 
> T&>::type boost::move(T&) [with T = boost::unique_future<long unsigned 
> int>]
>
> The offending line of code:
> futures.push_back(boost::move(taskResult));    // futures is a 
> boost::container::deque
>
> Is there a way to force one version of boost::move over the other?  If 
> so, which one should I use?
>
>
We have decided to adapt Boost.Thread to Boost.Move. Be patient, I 
expect this will be released in 1.50.

Best,
Vicente