You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/01/17 20:22:16 UTC

[GitHub] [arrow] ritchie46 edited a comment on pull request #9211: ARROW-11239: [Rust] Fixed equality with offsets and nulls

ritchie46 edited a comment on pull request #9211:
URL: https://github.com/apache/arrow/pull/9211#issuecomment-761873563


   > @rdettai I understand that concern. Could you describe which areas do you get more pain from backward incompatible changes? I would be fine with a 1 release deprecation when feasible, at least on the `arrow` crate.
   
   It is mostly about the (builder/buffer related) functionality being removed without no immediately clear substitute. For instance [ArrayBuilder::append_data](https://docs.rs/arrow/2.0.0/arrow/array/trait.ArrayBuilder.html#tymethod.append_data), and several other API methods/traits. Another one was `BooleanType` not being a primitive anymore (I can understand the reason behind it). My crate is using a lot of the API surface, and 3 months of accumulated changes can be a real mess at once. 
   
   I think that the first case would be less problematic if it were possible to get mutable references to some inner types, as I could rebuild some of the logic and gracefully update.


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org