Algorithm for copying a container of CaloHypo objects
Usually, one would copy CaloHypo
objects implicitly by copying ProtoParticle
objects with the CopyProtoParticles
algorithm, which copies all related objects (including CaloHypo
). But it's not the case that all CaloHypo
objects will be associated to at least one ProtoParticle
a priori, so if you want to make sure that a CaloHypo
container is copied completely you need an additional copy algorithm for CaloHypo
objects . This MR adds such an algorithm.
(The concrete use-case is PersistReco in HLT2.)
Merge request reports
Activity
mentioned in merge request !105 (merged)
I think it makes more sense to move all the code to the .cpp and remove .h
Edited by Rosen MatevI agree with @rmatev that a .cpp that is a single include statement feels wrong. Factory macros in headers are also rather non-standard, since it means this header can never be included in another compilation unit, which makes it effectively a .cpp.
I also agree with @apearce that consistency is important, but in this case I am leaning toward more sensible extensions.
mentioned in commit cfcc4dc1