You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2018/11/29 15:41:01 UTC
[jira] [Resolved] (ARROW-3169) [C++] Break array-test.cc and
array.cc into multiple compilation units
[ https://issues.apache.org/jira/browse/ARROW-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney resolved ARROW-3169.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.13.0)
0.12.0
Issue resolved by pull request 3047
[https://github.com/apache/arrow/pull/3047]
> [C++] Break array-test.cc and array.cc into multiple compilation units
> ----------------------------------------------------------------------
>
> Key: ARROW-3169
> URL: https://issues.apache.org/jira/browse/ARROW-3169
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.12.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> To improve readability I suggest splitting array-test.cc into multiple compilation units (which will still be linked into an executable {{array-test}}). We can do the same thing with array.h/array.cc, while maintaining the {{arrow/array.h}} public header. Some of these could go into {{arrow/columnar}} or {{arrow/impl}}, or something similar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)