fix: hide anonymous RNTuple fields by default #1469
Draft
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.
This PR hides the anonymous fields present in RNTuples. I made this a draft because I want to spend some more time thinking about this to make sure everything that people might want to access is actually easily accessible.
This is a rough first draft that has some downsides. For example, if you have a tuple field, the underlying data in each position of the tuple is stored in fields
_0, _1, ...
, so those would be hidden, but those should actually be accessible. Similarly, if you have an array of structs, let's say an array of electrons, then the members get stored in_0.pt, _0.eta, ...
, so again those would be hidden, but should actually be accessible.The tricky part that I'll have to figure out is how to separate "key paths" from the "real paths" inside the RNTuple (e.g.
electron.pt
vselectron._0.pt
).Thanks to @kratsg for bringing up this issue.