-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[v636][ntuple] Fix type names with [U]Long64_t template args #20600
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
Open
jblomer
wants to merge
8
commits into
root-project:v6-36-00-patches
Choose a base branch
from
jblomer:v636-ntuple-fix-int-templ
base: v6-36-00-patches
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[v636][ntuple] Fix type names with [U]Long64_t template args #20600
jblomer
wants to merge
8
commits into
root-project:v6-36-00-patches
from
jblomer:v636-ntuple-fix-int-templ
+227
−66
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Backport a minimal subset of the improvements of commit 705376f We don't backport part of the changes that implement RNTuple normalization of demangled paths. But we do apply some improvements to the renormalization of meta-normalized paths. This is a precondition to cleanly apply the series of patches fixing [U]Long64_t in template parameters.
This restriction is actually not required. (cherry picked from commit 0ce3049)
(cherry picked from commit 1648058)
Custom classes with [U]Long64_t template arguments need to use their meta-normalized name as type alias. Otherwise, during reconstruction with the RNTuple normalized name, the streamer info for the `std::[u]int64_t` argument will be requested (typically `long` instead of `long long`). (cherry picked from commit 6124192)
(cherry picked from commit 571411b)
(cherry picked from commit 9a821aa)
(cherry picked from commit cc32bb6)
Clarify treatment of ROOT fundamental typedefs, including special treatment of `[U]Long64_t`. (cherry picked from commit b140667)
Test Results 16 files 16 suites 2d 12h 4m 0s ⏱️ For more details on these failures, see this check. Results for commit 285eaed. |
silverweed
approved these changes
Dec 8, 2025
Contributor
silverweed
left a comment
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.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #20478
Non-trivial backport.