[Boost-bugs] [Boost C++ Libraries] #11231: Allow to set continuation future's destructor behavior to non-blocking

Subject: [Boost-bugs] [Boost C++ Libraries] #11231: Allow to set continuation future's destructor behavior to non-blocking
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2015-04-24 00:28:06

#11231: Allow to set continuation future's destructor behavior to non-blocking
-------------------------------------------+----------------------------
 Reporter:  Konrad Zemek <konrad.zemek@…>  |      Owner:  anthonyw
     Type:  Feature Requests               |     Status:  new
Milestone:  To Be Determined               |  Component:  thread
  Version:  Boost 1.58.0                   |   Severity:  Not Applicable
 Keywords:                                 |
-------------------------------------------+----------------------------
 As [http://thread.gmane.org/gmane.comp.lib.boost.user/83879 discussed on
 the mailing list]:

 Currently, continuation futures created using {{{future<>::then()}}} with
 {{{boost::launch::async}}} or an executor block on destruction (until the
 value is ready).

 I would like there to be a way to disable this behavior, whether through
 an additional argument in {{{future<>::then()}}} (much like
 {{{boost::defer_lock}}} in locks' constructors), a method explicitly
 setting the non-blocking behavior, or implicitly through a call to
 {{{future<>::wait_for/until()}}}.

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