min(NaN, 1.0) should return NaN

question

#1

Currently min(NaN, 1.0) returns 1.0. I think this is very unsafe. Is there a reason for this?

I feel strongly that min(NaN, 1.0) should return NaN instead.

The same applies to max and related functions, of course.


#2

#3

so it will be fixed in v6.0…