1
Fork 0

Rollup merge of #87419 - programmerjake:patch-1, r=nagisa

IEEE 754 is not an RFC

If there were something between `IEEE` and `754`, it would be `STD`: [`IEEE STD 754-2019`](https://doi.org/10.1109%2FIEEESTD.2019.8766229)
This commit is contained in:
Manish Goregaokar 2021-07-24 09:52:03 -07:00 committed by GitHub
commit 25fab0c8a7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -44,7 +44,7 @@ Libraries
- [`leading_zeros`, and `trailing_zeros` are now available on all - [`leading_zeros`, and `trailing_zeros` are now available on all
`NonZero` integer types.][84082] `NonZero` integer types.][84082]
- [`{f32, f64}::from_str` now parse and print special values - [`{f32, f64}::from_str` now parse and print special values
(`NaN`, `-0`) according to IEEE RFC 754.][78618] (`NaN`, `-0`) according to IEEE 754.][78618]
- [You can now index into slices using `(Bound<usize>, Bound<usize>)`.][77704] - [You can now index into slices using `(Bound<usize>, Bound<usize>)`.][77704]
- [Add the `BITS` associated constant to all numeric types.][82565] - [Add the `BITS` associated constant to all numeric types.][82565]