On Mon, 2021-04-26 at 23:28 -0700, christoph...@gmail.com wrote: > It seam that C is wrong on this one and Go is right. The rationale is > that a NaN must propagate through operations so that we can detect > problems (avoid silent NaNs). See https://en.wikipedia.org/wiki/NaN > > Thus any operation involving a NaN must return an NaN and this > includes Max and Min.
This is not what the IEEE 754 spec says for the behaviour of minNum and maxNum. Whether a language decides to implement their min and max functions according to the IEEE 754 spec is up to them. Note that Go uses non-signalling NaN's and claims to use IEEE 754 floating point numbers (https://golang.org/ref/spec#Numeric_types). So we'd expect it to have the behaviour specified in the 754 spec. This is why I asked the question. Jesper's answer highlighted subtlety that is worth considering. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7bbb6c9daf86ae6010a273d603cb9e4c9dae743b.camel%40kortschak.io.
