ThreadPool takes ownership of its jobs, but as far as I can tell,
TimeSliceThread does not. I could create something that receives callbacks when the
TimeSliceClient jobs are finished and then delete them manually, but this seems error prone.
I’m wondering if the fact that
TimeSliceThread doesn’t handle its own allocation is intentional, and I have misunderstood how it is supposed to work. I had assumed that you could add and remove clients dynamically, and fairly fast. Is it intended for this? If so, what is the recommended way for managing the lifetime of the clients?