-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-42126: [C++] Move TakeXXX free functions into TakeMetaFunction and make them private #42127
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
deb6309
TakeCAC: Extract TakeAAC for simpler delegation
felipecrv 4aa8992
Take: Pass ChunkedArray as shared_ptr& in TakeXXX functions
felipecrv 1a1d6ff
Take: Move all TakeXXX() functions to the TakeMetaFunction class
felipecrv 82e7585
Take: Review the TakeXXX delegation logic
felipecrv c27f54e
Take: Add TakeCAA, and remove TakeAAC
felipecrv 2a682cd
TakeMetaFunction: Make most static methods private
felipecrv fc99783
Take: Remove unwanted TODO comment
felipecrv File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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'm curious: is there a particular reason for taking the first arg as shared_ptr-const-ref, and the second only as value-const-ref?
Uh oh!
There was an error while loading. Please reload this page.
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.
Driven by the signatures of the
Datumconstructors [1]. Originally, they were almost all by simple&, then I tried making all of themshared_ptr&but that got overwhelming, so I settled on this mixed combination driven by the need (Arrayholdsshared_ptr<ArrayData>which is whatDatumcares about).[1]
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 want to simplify these signatures further in the next PR as less will actually have to be handled by the
"take"MetaFunction as"array_take"learns to handle chunked arrays by itself.