Re: [Boost-bugs] [Boost C++ Libraries] #2602: Error, inaccessible: boost::thread::thread(boost::thread&) is not accessible from ...

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2602: Error, inaccessible: boost::thread::thread(boost::thread&) is not accessible from ...
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-02-04 12:23:53

#2602: Error, inaccessible: boost::thread::thread(boost::thread&) is not
accessible from ...
---------------------------------------------------+------------------------
  Reporter:  Roberto Gimenez <chilabot_at_[hidden]>  |       Owner:  anthonyw
      Type:  Bugs                                  |      Status:  new     
 Milestone:  Boost 1.38.0                          |   Component:  thread  
   Version:  Boost 1.37.0                          |    Severity:  Problem 
Resolution:                                        |    Keywords:          
---------------------------------------------------+------------------------

Comment(by Jonathan Wakely <jwakely.boost_at_[hidden]>):

 IMHO the patch is an improvement, as it allows explicit moves from
 lvalues, even though it doesn't help with implicit moves from rvalues
 (because you can't create a boost::thread rvalue with the Sun compiler.)

 Looking into the unique_lock test failures (which don't cause a failure
 when building libboost_thread because there's no locks.cpp) I tried to
 find boost::move() for unique_lock, but it seems to only be defined in
 when BOOST_HAS_RVALUE_REFS, is that right?

 {{{
 #ifdef BOOST_HAS_RVALUE_REFS
     template<typename Mutex>
     inline unique_lock<Mutex>&& move(unique_lock<Mutex>&& ul)
     {
         return ul;
     }
 #endif
 }}}

 Should there be a #else ?

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/2602#comment:2>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.