wjgra / arq-benchmark

0 stars 0 forks source link

[util] Handle thread exceptions #4

Closed wjgra closed 1 month ago

wjgra commented 2 months ago

Exceptions thrown by server/client threads are currently uncaught - consider a ThreadContext class that includes an atomic<bool> shouldExit to manage thread lifetime.

wjgra commented 2 months ago

Redundant in view of #10 - we can just use std::futures instead, which propagate exceptions upon calls to get().

wjgra commented 1 month ago

Re-opened: the ordering imposed by get() means that an exception being thrown in a given thread does not terminate the program. This is worth investigating further.