I was under the impression that self-destruction was a feature we needed to support (hence the test). If we don't need it, I am fine with dropping it/making it an error like you suggest.
> Rather than passing in a reference to a promise, would it make more sense to
> have a method
> std::shared_future<void> shutdown_notifier()
> and have ~SimpleDispatchThread set_value_at_thread_exit() in the case of
> destruction-from-eventloop-thread?
Unfortunately g++ 4.9 doesn't support set_*_at_thread_exit.
> Another option would be to abort instead of detaching the thread; that's /code.launchpad .net/~raof/ mir/remove- eventloop- self- +merge/ 255767
> implemented here: https:/
> immolation/
I was under the impression that self-destruction was a feature we needed to support (hence the test). If we don't need it, I am fine with dropping it/making it an error like you suggest.
> Rather than passing in a reference to a promise, would it make more sense to future< void> shutdown_notifier() Thread set_value_ at_thread_ exit() in the case of from-eventloop- thread?
> have a method
> std::shared_
> and have ~SimpleDispatch
> destruction-
Unfortunately g++ 4.9 doesn't support set_*_at_ thread_ exit.