P0493R3 (
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p0493r3.pdf)
proposes atomic floating-point min/max based on std::min and std::max.

std::min and std::max are known to disagree with std::fmin/std::fmax for
things like signed zeros and NaN values.
I do not imagine a world where future C evolution will agree with the
std::min and std::max behaviour.

Have the appropriate groups discussed this?

Also, I believe the example implementations in the paper are erroneous in
relation to the presented wording.
For example, in section 5.1 of the paper, the operands to `max` are in the
wrong order.

-- HT