-
Notifications
You must be signed in to change notification settings - Fork 38
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
CellID is long long int
in DD4hep, but uint64_t
in EDM4hep
#202
Comments
Argh, that seems like an oversight in the original definition. Since it is used as a bitfield (in hopefully all cases), I wouldn't rule out a change of EDM4hep a priori. On the other hand since it is used as a bitfield potentially also DD4hep could profit from at least making this a fixed width integer instead of just Let's discuss this in a bit more detail in the next Key4hep meeting. We can then also take this to a DD4hep meeting to see how this can be reconciled. |
I prefer the change from
|
long long int
in DD4hep, but unsigned long long
in EDM4heplong long int
in DD4hep, but uint64_t
in EDM4hep
The signed'ness is probably not the issue, but it may be more interesting to specify the exact bitfield width already in the type rather rely on a less strict definition of "long long". |
Closing since the discussion moved to AIDASoft/DD4hep#1090, which has now been fixed |
There is a (potentially relevant) inconsistency between CellID in DD4hep and EDM4hep.
long long int
inDDCore/include/Parsers/Primitives.h
. https://github.com/AIDASoft/DD4hep/blob/master/DDCore/include/Parsers/Primitives.h#L44uint64_t
, e.g. in https://github.com/key4hep/EDM4hep/blob/master/edm4hep.yaml#L325This leads to some ergonomics issues in downstream code where care and explicit casts are needed. I understand (of course) that changing the EDM4hep side of this is hard considering the volume of stored data files. I also understand that changing DD4hep is potentially very invasive as well. So, I guess I'm just complaining ;-)
The text was updated successfully, but these errors were encountered: