about summary refs log tree commit diff
diff options
context:
space:
mode:
authorBrent Kerby <blkerby@gmail.com>2019-05-18 10:03:12 -0600
committerGitHub <noreply@github.com>2019-05-18 10:03:12 -0600
commit13a00963a6684455c129f19a643b65226f438f37 (patch)
tree0a2fa918be058566fe774dd714319189543a9c20
parentb8aa422a788c45c67d747346276d229d08925fe1 (diff)
downloadrust-13a00963a6684455c129f19a643b65226f438f37.tar.gz
rust-13a00963a6684455c129f19a643b65226f438f37.zip
fix copy-paste typo in docs for ptr::read_volatile
-rw-r--r--src/libcore/ptr.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/ptr.rs b/src/libcore/ptr.rs
index b6de9f57b01..ada784e9ce7 100644
--- a/src/libcore/ptr.rs
+++ b/src/libcore/ptr.rs
@@ -837,7 +837,7 @@ pub unsafe fn write_unaligned<T>(dst: *mut T, src: T) {
 ///
 /// * `src` must be properly aligned.
 ///
-/// Like [`read`], `read_unaligned` creates a bitwise copy of `T`, regardless of
+/// Like [`read`], `read_volatile` creates a bitwise copy of `T`, regardless of
 /// whether `T` is [`Copy`]. If `T` is not [`Copy`], using both the returned
 /// value and the value at `*src` can [violate memory safety][read-ownership].
 /// However, storing non-[`Copy`] types in volatile memory is almost certainly