the Slicer should not have its own thread pool

Description

In the current implementation, each Slicer object has its own thread pool. This could become a problem if someone does an implementation that starts an important number of Slicer in parallel. The Slicer should use the shared thread pool, currently called subtreeOperationsExecutor but that should be renamed as it is used for more than only subtree operations.

Status

Assignee

Gautier Berthou

Reporter

Gautier Berthou

Labels

None

Fix versions

Priority

Highest
Configure