[
https://issues.apache.org/jira/browse/ARROW-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719262#comment-16719262
]
Wes McKinney commented on ARROW-47:
-----------------------------------
That's an interesting approach.
In any case, I don't think there's a need to do anything very complicated right
now. The basic requirements are:
* A base type {{Scalar}} that exposes its type information, and nullness
* A public API for accessing values in concrete subclasses, including nested
types
So, a scalar analogue to the {{Array}} classes. Let's start with making sure we
can do things like {{Add(Array, Scalar)}}. The implementation details of the
data structure would best be encapsulated behind a public API for the time
being.
> [C++] Consider adding a scalar type object model
> ------------------------------------------------
>
> Key: ARROW-47
> URL: https://issues.apache.org/jira/browse/ARROW-47
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Wes McKinney
> Assignee: Uwe L. Korn
> Priority: Major
> Labels: Analytics
> Fix For: 0.13.0
>
>
> Just did this on the Python side. In later analytics routines, passing in
> scalar values (example: Array + Scalar) requires some kind of container. Some
> systems, like the R language, solve this problem with length-1 arrays, but we
> should do some analysis of use cases and figure out what will work best for
> Arrow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
