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-07 17:45:36

#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 a first analysis, I think that we need to use unique_ptr<T> instead
 of scoped_ptr<T>.
 The problem is that we need a type erased deleter so that we can
 instantiate with default_delete<T> and with a specific
 allocator_delete<T,A>.


 {{{
 unique_ptr<T, erased_delete<T>>
 }}}

 I will start by refactoring the code, so that it is possible to set the
 value using an erased unique_ptr<> instead of the current
 source_reference_type and rvalue_source_type.

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