Github user bavardage commented on the issue:
https://github.com/apache/spark/pull/21794
yep fair - the intent I think was clarity rather than necessarily perf:
it's misleading to have a method named 'nan safe' which has no special handling
of nans. I'll look at opening a different PR which could increase clarity/may
have minor perf benefit.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
