[14x-comb2023] Avoid invalid proxy constructor calls in HMuMuRooPdfs #893
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the
HMuMuRooPdfs
, there was a classic dangerous RooFit mistake.There were constructor calls like:
However, this is not doing what one would naively expect, which is
having proxy to a constant. Instead, it will hit this constructor by
converting the
double
tobool
, which is used as thevalueServer
parameter:
https://root.cern/doc/v626/classRooTemplateProxy.html#a9a550633b5336561b48eb313994a68e8
So it will create a proxy to nothing! In this particular case, this was
not a problem because in
evaluate()
, there is a fallback for emptyproxies.
But ROOT 6.30 makes some compile-time checks to prevent these mistakes,
so this commit is necessary to compile with newer ROOT versions.
See https://root.cern/doc/v626/classRooTemplateProxy.html.