about summary refs log tree commit diff
path: root/src/libstd
diff options
context:
space:
mode:
authorMazdak Farrokhzad <twingoow@gmail.com>2019-07-22 15:32:23 +0200
committerGitHub <noreply@github.com>2019-07-22 15:32:23 +0200
commitb94e59cc41f8eeb36ee269cae3275d7620189c14 (patch)
tree2229cbae499f370a4acc34a96e74967a32f88cf5 /src/libstd
parent12896778219a06cf4c16cfae877b882555a200af (diff)
parent8dc5635e13c608757cf0c9c99dac747ed334fbe9 (diff)
downloadrust-b94e59cc41f8eeb36ee269cae3275d7620189c14.tar.gz
rust-b94e59cc41f8eeb36ee269cae3275d7620189c14.zip
Rollup merge of #62845 - RalfJung:read, r=rkruppe
read: fix doc comment

No idea how that happened...
Diffstat (limited to 'src/libstd')
-rw-r--r--src/libstd/io/mod.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libstd/io/mod.rs b/src/libstd/io/mod.rs
index a8d4d1181aa..e951b575773 100644
--- a/src/libstd/io/mod.rs
+++ b/src/libstd/io/mod.rs
@@ -511,8 +511,8 @@ pub trait Read {
     ///
     /// Correspondingly, however, *callers* of this method may not assume any guarantees
     /// about how the implementation uses `buf`. The trait is safe to implement,
-    //  so it is possible that the code that's supposed to write to the buffer might also read
-    //  from it. It is your responsibility to make sure that `buf` is initialized
+    /// so it is possible that the code that's supposed to write to the buffer might also read
+    /// from it. It is your responsibility to make sure that `buf` is initialized
     /// before calling `read`. Calling `read` with an uninitialized `buf` (of the kind one
     /// obtains via [`MaybeUninit<T>`]) is not safe, and can lead to undefined behavior.
     ///