-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: mv id() to getObjectID().index because id() returns ObjectID, not uint_t, in podio v0.17.1 #1106
Conversation
…, not uint_t This adds forward compatibility with podio v0.17.1 See AIDASoft/podio#493
462e86b
to
ef9e08b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For correctness sake, we should be leaning towards full object id comparisons where possible. This looks correct, still.
Fortunately that is already the case in several other places. I didn't (need to) replace those cases because the ObjectID comparison works fine. It's only the places where the ObjectID is explicitly assumed to be a uint_t (for storing or debug output) that are modified here. |
Successfully created backport PR for |
…rns ObjectID, not uint_t, in podio v0.17.1 (#1109) # Description Backport of #1106 to `v1.7`. --------- Co-authored-by: Wouter Deconinck <[email protected]>
Briefly, what does this PR introduce?
This adds forward compatibility with podio v0.17.1. See AIDASoft/podio#493
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No.
Does this PR change default behavior?
No. The modified algorithms are not relying on the most significant bits in the previous ObjectID uint_t that encode the collectionID.