- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Mar 2022 19:17:20 +0000
- To: public-css-archive@w3.org
> Once you have NaN values, they tend to break a lot of developer assumptions (e.g., again assuming IEEE 754 / IEC 559), such as breaking the assumption that one of a < b, a == b, and a > b is true. Note that we don't (yet) have direct comparisons, and the functions that do comparison-like things (clamp/min/max) all evaluate to NaN if they have a NaN argument (see the final bulleted item in the list of division by zero consequences in [Values 4, section 10.9 Type Checking](https://andreubotella.com/csswg-auto-build/css-values-4/#calc-type-checking), so at least we currently avoid the most obvious NaN confusions. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7067#issuecomment-1082276073 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 March 2022 21:08:11 UTC