You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by "viirya (via GitHub)" <gi...@apache.org> on 2023/04/02 22:27:24 UTC

[GitHub] [arrow-rs] viirya commented on issue #3999: Improved Temporal and Decimal Arithmetic

viirya commented on issue #3999:
URL: https://github.com/apache/arrow-rs/issues/3999#issuecomment-1493454958

   I think for a trait approach, the advantage would be a cleaner implementation. It might be easier to maintain for long term. The concerns I have are basically: 1. performance. I'm not sure if such trait-based dispatch could bring performance penalty even it is slight. 2. special needs. Adding arcane method names is because there are special needs for computation (e.g. checked, opt, overflow-allowing, etc). In order to match such requirements, I think one trait is not necessary but it will lead to some special traits for special need. So eventually we might still have arcane trait names 😂 .


-- 
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: github-unsubscribe@arrow.apache.org

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