zanmato1984 commented on issue #46063:
URL: https://github.com/apache/arrow/issues/46063#issuecomment-3056332972

   From the implementation perspective, I think the cheapest and reasonable 
solution is that we do:
   ```
   min([]) == null;
   min([nan, nan, nan]) == nan;
   min([nan, nan, 42.0)] == 42.0;
   ```
   We can simply initialize the running min/max to nan (instead of -inf/inf) 
and leverage the nice property of `fmin/fmax` that for all two nans return nan, 
otherwise the non-nan. And allowing empty array and all-nan array, that would 
be otherwise considered invalid in NumPy, shouldn't be much of a harm perhaps?


-- 
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-unsubscr...@arrow.apache.org

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

Reply via email to