Custom setPtr instantiations not honored
With the change from art 2 to art 3, the template instantiations provided by mu2e's
OwningPointerCollection are no longer picked up by the compiler, resulting in incorrect results. Analysis should be done whether this is a bug in
art, or whether there are simple changes in mu2e code that can fix this error.
#1 Updated by Kyle Knoepfel 9 months ago
The problem is understood. A line of code deep within art (
canvas, actually), changed from calling
art::setPtr(...). The explicit
'art::' qualification thus discarded the customized
mu2e::setPtr template specialization that Mu2e has provided for the
mu2e::OwningPointerCollection. The customized behavior is restored by removing the explicit
This fix requires a new art release. We have other bug fixes ready to go in, so we would like to release an
art 3.02 bug-fix release. Does that sound reasonable?