Feature: provide a way to shutdown the thread pool

[mattgathu]

It would be great to provide a mechanism to terminate all pending tasks and wait for the current one to complete.

Essentially complete the current executing jobs (since I'm not sure it's possible to terminate spawned threads). And then don't proceed doing any more work.

At the moment this is not possible.

[dns2utf8]

Hi Matt

I think this feature would be great. What behaviour would you expect?
That after the stop_queue()/abort_pool() the queue is drained in the sense that all jobs up to this point are removed/ignored and new jobs are executed?
Or that the whole pool gets stopped forever?

I will think a bit more about it as well.

Cheers,
Stefan

[mattgathu]

Or that the whole pool gets stopped forever?

This is my expected behaviour

My use case, for example, is an application that might get quit signals for the OS e.g. the Ctrl-C keyboard interrupt. Once I get this signal, I would like to gracefully shutdown the thread pool.

[dns2utf8]

With the design of 2.0 you will be able to shutdown generations of tasks.
So without knowing anything about the function running in the pool as soon as it is finished it will run out allowing for a proper shutdown of the pool.