Reconsider setting termination handlers #406
Labels
effort: 2
A few hours of work.
priority: medium
This should be done sooner or later.
type: cleanup
type: feature
type: refactoring
Milestone
Setting the termination handlers does have value because we can print e.g. stacktraces which are not printed by default on segfaults, pika thread-specific information etc.
On the other hand, when pika is embedded in an application behind multiple other libraries, combined with other runtimes etc. who is to say that pika's termination handler is the termination handler to install?
Some in-between solutions would be to allow users to disable/enable pika's termination handler explicitly (with config options or explicit function calls).
The text was updated successfully, but these errors were encountered: