-
Notifications
You must be signed in to change notification settings - Fork 25
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
[c++,r,python] Move nanoarrow
to src/external
#2383
Conversation
This pull request has been linked to Shortcut Story #44473: [c++] Mnve |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2383 +/- ##
==========================================
- Coverage 66.04% 65.36% -0.69%
==========================================
Files 144 144
Lines 13000 12998 -2
Branches 511 509 -2
==========================================
- Hits 8586 8496 -90
- Misses 4314 4414 +100
+ Partials 100 88 -12
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Thank you!
closes #2362
Issue and/or context:
As described in #2362 the initial location of the three vendored
nanoarrow
files was just a first, placing them intosrc/external
is better (and the upcoming version 0.5.0 ofnanoarrow
should allow it also (more easily) an external cmake project.Changes:
The files have been moved, restored to their pristine release 0.4.0 form (undoing our formatting), and include and config locations have been adjusted.
Notes for Reviewer:
There may be smoother ways to do this, I would be more than happy to accommodate change requests from anybody deeper into CMake and Python than I am.
SC 44473