Re: [Boost-bugs] [Boost C++ Libraries] #8674: Futures as local named objects can't be returned with implicit move.

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8674: Futures as local named objects can't be returned with implicit move.
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-06-09 11:08:10

#8674: Futures as local named objects can't be returned with implicit move.
-------------------------------+----------------------
  Reporter:  mjklaim@…         |      Owner:  viboes
      Type:  Bugs              |     Status:  assigned
 Milestone:  To Be Determined  |  Component:  thread
   Version:  Boost 1.53.0      |   Severity:  Problem
Resolution:                    |   Keywords:
-------------------------------+----------------------

Comment (by mjklaim@…):

 I checked by debugging step-by-step the std::future behaviour and it does
 use the move constructor, not the other one.
 So no, it's not using the base-copy constructor.

 Maybe boost.thread futres's move-only macro is hiding the move constructor
 in some ways?

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