tustvold commented on issue #9184: URL: https://github.com/apache/arrow-rs/issues/9184#issuecomment-3754431587
IMO the issue appears to be that Array is getting used for two different use-cases: 1. A description of an array in arrow data format 2. A generic data container These are somewhat incompatible goals, in order for the former to work the set of types should be closed, which naturally precludes them being used as a generic data container. Even if we did make the trait unsafe, the constraints we would need to put on it would likely preclude the linked usages as a generic data container. Taking a step back, I wonder if we can find some other way to support these use-cases. I will confess to not knowing the intricacies of CUDF to be able to weigh in with what is appropriate there, but w.r.t range_array is there a reason this can't just be a StructArray with two children - and perhaps a piece of field metadata to identify its "logical" type? @waynexia -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
