owner, component changed

John Maddock — Thu, 31 Mar 2016 08:14:44 GMT

owner changed from John Maddock to Anthony Williams
component TR1 → thread

status, type changed; resolution set; milestone deleted

viboes — Tue, 09 Aug 2016 00:30:28 GMT

status new → closed
type Bugs → Feature Requests
resolution → wontfix
milestone To Be Determined

I can not take this in account unless boost::exception_ptr accepts std::exception_ptr

joseph@… — Tue, 23 Jan 2018 16:30:07 GMT

Is there some reason you can't add a #define to use std::exception_ptr instead of boost::exception_ptr? The 2 are totally incompatible so any system libraries using std::exception_ptr (such as ISO/IEC TS 22277:2017 coroutines) become a real burden to use with boost future (which has many wonderful features std::future does not). There does not appear to be a way to reliably convert between std::exception_ptr and boost::exception_ptr and the limited method I have found requires throwing 2 additional times which is really wasteful.

namespace boost
{
  template <>
  inline
    exception_ptr copy_exception(std::exception_ptr const &ex)
  {
    try {
      std::rethrow_exception(ex);
    }
    catch (const std::exception& e) {
      try {
        throw boost::enable_current_exception(e);
      }
      catch (...) {
        return boost::current_exception();
      }
    }
    catch (...) {
      try {
        throw boost::enable_current_exception(std::runtime_error("unknown exception"));
      }
      catch (...) {
        return boost::current_exception();
      }
    }
  }
}

Boost C++ Libraries: Ticket #12105: Support std::exception_ptr in boost::promise set_exception ??

owner, component changed

status, type changed; resolution set; milestone deleted