Re: [Boost-users] State of context and coroutine

Subject: Re: [Boost-users] State of context and coroutine
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2016-07-06 04:10:28

2016-07-06 9:49 GMT+02:00 Michael Steinberg <michsteinb_at_[hidden]>:

>
> 2016-07-05 20:36 GMT+02:00 Michael Steinberg <michsteinb_at_[hidden]>:
>
>> a) not documented
>
>
>
> http://www.boost.org/doc/libs/1_61_0/libs/coroutine2/doc/html/coroutine2/coroutine/asymmetric.html
> 'Code executed by *coroutine-function* must not prevent the propagation
> of the *detail::forced_unwind* exception. Absorbing that exception will
> cause stack unwinding to fail. Thus, any code that catches all exceptions
> must re-throw any pending *detail::forced_unwind* exception.'
>
> Oh well, I should have noted that we're going directly with
> context::execution_context now, in whose documentation I could not find
> this.
>

execution_context does not unwind the stack - the user is responsible for
this
http://www.boost.org/doc/libs/1_61_0/libs/context/doc/html/context/ecv2.html
'Sometimes it is necessary to unwind the stack of an unfinished context to
destroy local stack variables so they can release allocated resources (RAII
pattern). The user is responsible for this task.'