Currently each effect is interpreted using its own process and thread pools. It would be preferable to enable the caller to control the lifecycle of these pools. Concretely, we could change the signature of functions that introduce the dependency on a thread or process pool to e.g:
Currently each effect is interpreted using its own process and thread pools. It would be preferable to enable the caller to control the lifecycle of these pools. Concretely, we could change the signature of functions that introduce the dependency on a thread or process pool to e.g:
Where HasProcessPool is defined as: