tustvold commented on PR #6300:
URL: https://github.com/apache/arrow-rs/pull/6300#issuecomment-2328507438

   > We keep a lot of Arrow data in long-lived memory storage, and therefore 
must be guaranteed that the data has been optimized for space before it gets 
committed to storage, regardless of how it got built or how it got there.
   
   I think that would be generally useful, and would also handle the case of 
sliced arrays. I'd recommend something that returns a new Array, e.g. `fn 
shrink_to_fit(&self) -> ArrayRef`. You could also provide a strongly typed 
non-trait version, much like we do for slice.


-- 
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]

Reply via email to