Avoid direct dependency of optimiser to OPAL?
See also discussion on commit 5d045b26, in order not to forget I thought it would be good to open an issue. Commit 5d045b26 introduced a direct dependency of the optimiser to OPAL.
Two solutions were proposed:
Question is if we want to keep the option of having the optimiser stand alone?