diff options
| author | Alexis Bourget <alexis.bourget@gmail.com> | 2020-10-13 00:52:01 +0200 |
|---|---|---|
| committer | Alexis Bourget <alexis.bourget@gmail.com> | 2020-11-30 21:18:55 +0100 |
| commit | b3b1e0c224eb0ec025a903f58b219513ff5d8807 (patch) | |
| tree | a9985712a850b5813f1bde190891fe56c0311e64 | |
| parent | 4e54b4c3e67aa1b9aebb36e43ff00343155954d8 (diff) | |
| download | rust-b3b1e0c224eb0ec025a903f58b219513ff5d8807.tar.gz rust-b3b1e0c224eb0ec025a903f58b219513ff5d8807.zip | |
Intra doc links for f32/f64
| -rw-r--r-- | library/core/src/num/f32.rs | 10 | ||||
| -rw-r--r-- | library/core/src/num/f64.rs | 10 |
2 files changed, 10 insertions, 10 deletions
diff --git a/library/core/src/num/f32.rs b/library/core/src/num/f32.rs index 33df175bfc5..5f335b73e9b 100644 --- a/library/core/src/num/f32.rs +++ b/library/core/src/num/f32.rs @@ -776,8 +776,8 @@ impl f32 { /// As the target platform's native endianness is used, portable code /// should use [`to_be_bytes`] or [`to_le_bytes`], as appropriate, instead. /// - /// [`to_be_bytes`]: #method.to_be_bytes - /// [`to_le_bytes`]: #method.to_le_bytes + /// [`to_be_bytes`]: prim@f32::to_be_bytes() + /// [`to_le_bytes`]: prim@f32::to_le_bytes() /// /// # Examples /// @@ -804,7 +804,7 @@ impl f32 { /// /// [`to_ne_bytes`] should be preferred over this whenever possible. /// - /// [`to_ne_bytes`]: #method.to_ne_bytes + /// [`to_ne_bytes`]: prim@f32::to_ne_bytes() /// /// # Examples /// @@ -864,8 +864,8 @@ impl f32 { /// likely wants to use [`from_be_bytes`] or [`from_le_bytes`], as /// appropriate instead. /// - /// [`from_be_bytes`]: #method.from_be_bytes - /// [`from_le_bytes`]: #method.from_le_bytes + /// [`from_be_bytes`]: prim@f32::from_be_bytes() + /// [`from_le_bytes`]: prim@f32::from_le_bytes() /// /// # Examples /// diff --git a/library/core/src/num/f64.rs b/library/core/src/num/f64.rs index b85e8deb6d2..271671d14ef 100644 --- a/library/core/src/num/f64.rs +++ b/library/core/src/num/f64.rs @@ -790,8 +790,8 @@ impl f64 { /// As the target platform's native endianness is used, portable code /// should use [`to_be_bytes`] or [`to_le_bytes`], as appropriate, instead. /// - /// [`to_be_bytes`]: #method.to_be_bytes - /// [`to_le_bytes`]: #method.to_le_bytes + /// [`to_be_bytes`]: prim@f64::to_be_bytes() + /// [`to_le_bytes`]: prim@f64::to_le_bytes() /// /// # Examples /// @@ -818,7 +818,7 @@ impl f64 { /// /// [`to_ne_bytes`] should be preferred over this whenever possible. /// - /// [`to_ne_bytes`]: #method.to_ne_bytes + /// [`to_ne_bytes`]: prim@f64::to_ne_bytes() /// /// # Examples /// @@ -878,8 +878,8 @@ impl f64 { /// likely wants to use [`from_be_bytes`] or [`from_le_bytes`], as /// appropriate instead. /// - /// [`from_be_bytes`]: #method.from_be_bytes - /// [`from_le_bytes`]: #method.from_le_bytes + /// [`from_be_bytes`]: prim@f64::from_be_bytes() + /// [`from_le_bytes`]: prim@f64::from_le_bytes() /// /// # Examples /// |