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

owner, status changed

viboes — Fri, 24 Apr 2015 21:42:44 GMT

owner changed from Anthony Williams to viboes
status new → assigned

milestone changed

viboes — Sat, 17 Oct 2015 22:38:39 GMT

milestone To Be Determined → Boost 1.60.0

https://github.com/boostorg/thread/commit/88ab663ac58a2a903ee26b47a4eedb57535c4d14

status changed; resolution set

viboes — Wed, 21 Oct 2015 22:18:28 GMT

status assigned → closed
resolution → fixed

4321b59c1eedde71da58f592aa4c741a1feff046

anonymous — Tue, 22 Mar 2016 14:20:27 GMT

The blocking option seems to be broken. Future destructor doesn't block even if BOOST_THREAD_FUTURE_BLOCKING is defined and the futture was obtained by a call to boost::async() with boost::launch::async, or by calling other_future.then().

int main()
{
    {
        auto future = boost::async(boost::launch::async, []() {
            std::this_thread::sleep_for(1s);
            return 42;
        });
    } //future destructor doesn't block
    //do stuff...
    //-> will heppen before the future state is ready
}

anonymous — Wed, 13 Jul 2016 10:49:04 GMT

Replying to anonymous:

The blocking option seems to be broken. Future destructor doesn't block even if BOOST_THREAD_FUTURE_BLOCKING is defined and the futture was obtained by a call to boost::async() with boost::launch::async, or by calling other_future.then().
int main()
{
    {
        auto future = boost::async(boost::launch::async, []() {
            std::this_thread::sleep_for(1s);
            return 42;
        });
    } //future destructor doesn't block
    //do stuff...
    //-> will heppen before the future state is ready
}

The future destructor is never called even though the variable 'future' goes out of scope. See ticket #12220 for details.