[ https://issues.apache.org/jira/browse/ARROW-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe L. Korn resolved ARROW-2521. -------------------------------- Resolution: Fixed Issue resolved by pull request 1971 [https://github.com/apache/arrow/pull/1971] > [Rust] Refactor Rust API to use traits and generics > --------------------------------------------------- > > Key: ARROW-2521 > URL: https://issues.apache.org/jira/browse/ARROW-2521 > Project: Apache Arrow > Issue Type: Improvement > Components: Rust > Reporter: Andy Grove > Assignee: Andy Grove > Priority: Major > Labels: pull-request-available > Fix For: 0.10.0 > > Time Spent: 6h 50m > Remaining Estimate: 0h > > Early on, [~kszucs] and I worked on two different designs for how to > represent Arrow arrays in Rust, each with their pros and cons. > Krisztian started out with a generics approach e.g. Array<T> which was great > until we tried to implement structs, which can contain mixed types so we > ended up using enum to represent arrays, which was great until I got to the > list types ... I don't think I can implement nested lists with this approach. > I am reviewing this again now that I am more familiar with Arrow and also my > Rust skills have improved greatly since I started working on all of this. > I will be prototyping in a separate repo, and will update this Jira once I > have something concrete to share, but I feel it is important to address this > before the first official release of the Rust version. Also, if we are going > to consider a refactor like this, it is better to do it now while the > codebase is tiny. > > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)