|
Boost : |
Subject: [boost] [move] [ thread] ambiguous call to overloaded function
From: Tal Agmon (tal.boost_at_[hidden])
Date: 2011-03-24 08:28:22
Hello,
Did anyone experience the following
Revision 70494
tested on msvc2010
with headers the following headers:
[code]
#include< boost/thread.hpp>
#include < boost/move.hpp >
...
X x;
boost::packaged_task<string_ptr_type> pt(boost::bind(&X::foo,
boost::ref(x)));
boost::unique_future<string_ptr_type> fs = pt.get_future();
boost::thread task(boost::move(pt));
fs.wait();
...
[code]
outputs:
.$(BOOST_ROOT)boost/move/move.hpp(304): could be 'boost::packaged_task<R>
&boost::move<boost::packaged_task<R>>(T &)'
or
$(BOOST_ROOT)boost/thread/detail/move.hpp(44): or
'boost::detail::thread_move_t<T> boost::move<boost::packaged_task<R>>(T &)'
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk