Follow-up from "Propagate changes from CaloFutureShowerOverlapTool"

The following discussion from !1592 (merged) should be addressed:

  • @cmarinbe started a discussion:

    It was suggested to change the signature to const LHCb::CaloCluster& c1, const LHCb::CaloCluster& c2, ... so that it becomes the responsibility of the caller to pass a valid object. To be done.

Edited by Carla Marin Benito
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information