-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[ntuple] Ensure type name given by RField<T> is renormalized #17986
base: master
Are you sure you want to change the base?
[ntuple] Ensure type name given by RField<T> is renormalized #17986
Conversation
Test Results 19 files 19 suites 5d 5h 3m 29s ⏱️ For more details on these failures, see this check. Results for commit 209a806. ♻️ This comment has been updated with latest results. |
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.
I believe we need the same treatment for RField
inheriting from RProxiedCollectionField
950713d
to
f6566b3
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.
LG from my side
To avoid inconsistencies between the full type name of a custom class reported by the RNTuple IO and the type name reported by ROOT meta. The commit adds a unittest. Previously, the test would fail with exceptions such as: ``` 321: unknown file: Failure 321: C++ exception with description "type mismatch for field f2: DataVector<std::int32_t,std::vector<CustomStruct>> vs. DataVector<int,vector<CustomStruct> > 321: At: 321: void ROOT::Experimental::REntry::EnsureMatchingType(RFieldToken) const [with T = DataVector<int, std::vector<CustomStruct> >] 321: " thrown in the test body. ``` Co-authored-by: Jonas Hahnfeld <[email protected]>
f6566b3
to
209a806
Compare
To avoid inconsistencies between the full type name of a custom class reported by the RNTuple IO and the type name reported by ROOT meta. The commit adds a unittest. Previously, the test would fail with exceptions such as: