Rytis Karpuška

Hey, We would also like to test `boost::future` for `zk::future` implementation and I was poking around looking how difficult it is to add support for it. Unfortunately boost's exception handling...

> What version of Boost are you using that you see the problems? I use version from ubuntu 18.04 repos (which is 1.65.1), and I believe I did a quick...

While I was trying to understand this issue, I have written myself a quick, small [program](https://gist.github.com/Jauler/f0222fa70eec1edeb0c01eb4133e701a) to test boost exception handling. Notice `struct my_error` does not have `final` specifier. I...

So I decided to dig a little bit deeper. When `boost::current_exception()` is called, internally it maps to [boost::current_exception_impl()](https://github.com/boostorg/exception/blob/f1af13409d6cd08b24f8fb9a8f1b0f9dffba6a6d/include/boost/exception/detail/exception_ptr.hpp#L304), which in turn calls [boost::exception_detail::clone_current_exception()]( https://github.com/boostorg/exception/blob/f1af13409d6cd08b24f8fb9a8f1b0f9dffba6a6d/src/clone_current_exception_non_intrusive.cpp#L307) this function returns `exception_detail::clone_current_exception_result::not_supported` (more on...

Well I have a few cases: - input - some internal processing nodes - output Internal processing nodes are the simplest ones, therefore I described them in my original message,...

Hi, Unfortunately, I have no access to the original case. But I remember I was unable to extend the receiver class due to it having non-virtual methods. Therefore the current...