Skip to content

[6.36][ntuple] use only "true type name" for class members#21437

Open
jblomer wants to merge 1 commit intoroot-project:v6-36-00-patchesfrom
jblomer:ntuple-v636-fix-type-alias-member
Open

[6.36][ntuple] use only "true type name" for class members#21437
jblomer wants to merge 1 commit intoroot-project:v6-36-00-patchesfrom
jblomer:ntuple-v636-fix-type-alias-member

Conversation

@jblomer
Copy link
Contributor

@jblomer jblomer commented Feb 28, 2026

Backport of #21373

@jblomer jblomer self-assigned this Feb 28, 2026
@jblomer jblomer requested a review from pcanal as a code owner February 28, 2026 21:42
@jblomer jblomer force-pushed the ntuple-v636-fix-type-alias-member branch from 475af1a to 106ee5d Compare February 28, 2026 22:40
Do not set the full type name as type alias. Pass only the true type
name to RFieldBase::Create(). The true type name will contain Long64_t
and Double32_t type name tokens, so we are still able to treat those
correctly.

The full type name would provide additional information. However,
normalizing the full type name can cause header auto parsing. Also, the
full type name, in general, cannot be used directly because it may be
a type that is only valid within the class context.

(cherry picked from commit 054886d)
@github-actions
Copy link

github-actions bot commented Mar 1, 2026

Test Results

    17 files      17 suites   2d 8h 27m 17s ⏱️
 2 752 tests  2 752 ✅ 0 💤 0 ❌
45 192 runs  45 192 ✅ 0 💤 0 ❌

Results for commit 106ee5d.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant