-
Feature gate: `#![feature(float_minimum_maximum)]`
This is the tracking issue for the `f{32,64}::{min,max}imum` functions.
It provide IEEE 754-2019 `minimum` and `maximum` functions to f32/f64.
###…
-
As per the FAQ 😉
-
In the "References" section, the W3C version of the specification contains a reference to IEEE 754-2008 instead of IEEE 754-2019. Browser and PDF versions do not have this problem.
-
# 总结
- https://baike.baidu.com/item/IEEE%20754/3869922?fr=aladdin
- https://segmentfault.com/a/1190000008268668
- **这里说的是浮点数,整型使用的是补码表示**
- **为什么JS使用IEEE 754? 因为C语言就是用IEEE 754标准**
- 是20世纪80年代以来最广…
cisen updated
3 years ago
-
Ok, maybe you don't even wanna support this. But it would be nice to specify if this is on purpose.
Aeson 2 can roundtrip plus/minus infinity and NaN just fine:
```
repl> Data.Aeson.decode @Dou…
-
Relates to https://github.com/webmachinelearning/webnn/issues/252
Some accelerators use non-standard float point types (e.g. bfloat16 and TF32). They are important to achieve high performance (e.g.…
-
Check the changes between 1985 and 2008 version of spec and add comments here if 377-1 is impacted
-
@thestinger filed https://github.com/mozilla/rust/issues/9987, and I thought we should get the ball rolling on documenting and testing IEEE 754-2008 compliance for Rust on non-embedded platforms.
I d…
-
Do we have a FAQ-like/best practices document? I'd like to see the question: "How do I represent IEEE-754 non-finite numbers like `Nan` or `Infinity` in IPLD?
I guess the answer is something along …
-
IEEE-754 requires that all comparisons between NaN and any other number (including NaN) return false (except not-equals, which naturally returns true). Elm, however, returns true for both NaN > NaN a…