You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 4948 Reporter:@dbuenzli Status: closed (set by @xavierleroy on 2015-12-11T18:04:29Z) Resolution: won't fix Priority: normal Severity: tweak Version: 3.11.1 Category: documentation Related to:#5038 Monitored by:@dbuenzli@Chris00
Bug description
The documentation makes it sound like there exists a single NaN value.
The following improvements could be done :
In the documentation of compare, note that compare equates all NaN value.
In the paragraph preceding floating point functions, indicate that
0. /. 0. returns a NaN value (instead of Pervasives.nan) and that
any function taking a NaN (instead of Pervasives.nan) value returns a
NaN value (instead of Pervasives.nan).
In the documentation of Pervasives.nan, indicate that nan is a NaN value
but that may not be the one you get in 0. /. 0.
The text was updated successfully, but these errors were encountered:
Yes, IEEE 754 allows for multiple NaN values, and I've never seen a program take advantage of that. But the point is that all these NaNs are not distinguishable from Caml: as you noticed, they compare equal according to Pervasives.compare. So, I don't see the need to complicate the documentation to talk about something that is invisible to the programmer.
Original bug ID: 4948
Reporter: @dbuenzli
Status: closed (set by @xavierleroy on 2015-12-11T18:04:29Z)
Resolution: won't fix
Priority: normal
Severity: tweak
Version: 3.11.1
Category: documentation
Related to: #5038
Monitored by: @dbuenzli @Chris00
Bug description
The documentation makes it sound like there exists a single NaN value.
The following improvements could be done :
0. /. 0. returns a NaN value (instead of Pervasives.nan) and that
any function taking a NaN (instead of Pervasives.nan) value returns a
NaN value (instead of Pervasives.nan).
but that may not be the one you get in 0. /. 0.
The text was updated successfully, but these errors were encountered: