Implement AnyRee#9959
Open
Rich-T-kid wants to merge 3 commits intoapache:mainfrom
Open
Conversation
Jefffrey
reviewed
May 11, 2026
Rich-T-kid
force-pushed
the
rich-T-kid/Ree-AnyArray
branch
from
f398606 to
d626ef8
Compare
Rich-T-kid
force-pushed
the
rich-T-kid/Ree-AnyArray
branch
from
d626ef8 to
b7e7b73
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue does this PR close?
closes #9909.
AnyRunArraytrait #9909.Rationale for this change
makes the API simpler to work with & less code duplication
What changes are included in this PR?
Replace the per-key-type RunEndEncoded match arms in length/bit_length (arrow-string) and date_part (arrow-arith) with a single dispatch through the new
AsArray::as_any_ree_opt/as_any_reereturning &dyn AnyRunEndArray, mirroring the existing dictionary handling. This removes thenow-unused
ree_map!macro, leaving one trait-object code path for all Int16/Int32/Int64 run-end types.Are these changes tested?
yes
Are there any user-facing changes?
no