Re: [Boost-bugs] [Boost C++ Libraries] #9425: Boost promise & future does not use supplied allocator for value storage

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #9425: Boost promise & future does not use supplied allocator for value storage
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2014-09-09 06:27:01

#9425: Boost promise & future does not use supplied allocator for value storage
-------------------------------+----------------------------------------
  Reporter:  ned14             |      Owner:  viboes
      Type:  Bugs              |     Status:  assigned
 Milestone:  To Be Determined  |  Component:  thread
   Version:  Boost 1.55.0      |   Severity:  Problem
Resolution:                    |   Keywords:  promise, future, allocator
-------------------------------+----------------------------------------

Comment (by viboes):

 After some trials, I have fall on issues mixing the old Boost.Thread move
 emulation and boost::movelib_unique_ptr<T,D>, which is of course not aware
 of this old emulation.

 I suspect that this issue could only be fixed on a version that doesn't
 supports the old move emulation.

 I'm wondering if it will be a good idea to branch a specific future.hpp
 implementation that doesn't supports the old move semantics and is aligned
 with version 4.

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