From 7656e085e3d056f0f0f35a9112727478a848350f Mon Sep 17 00:00:00 2001 From: Dan Gohman Date: Wed, 8 Jun 2022 08:24:28 -0700 Subject: [PATCH] Reword a question into a statement. --- library/std/src/os/unix/io/mod.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/library/std/src/os/unix/io/mod.rs b/library/std/src/os/unix/io/mod.rs index bc2f6b7659f..8935f303081 100644 --- a/library/std/src/os/unix/io/mod.rs +++ b/library/std/src/os/unix/io/mod.rs @@ -52,8 +52,8 @@ //! and writes happen outside the control of the Rust compiler, so they do not //! uphold Rust's memory safety guarantees. //! -//! Does this mean that all APIs that might allow `/proc/self/mem` to be opened -//! and read from or written to must be `unsafe`? No. Rust's safety guarantees +//! However, this does not mean that all APIs that might allow `/proc/self/mem` +//! to be opened and read from or written must be `unsafe`. Rust's safety guarantees //! only cover what the program itself can do, and not what entities outside //! the program can do to it. `/proc/self/mem` is considered to be such an //! external entity, along with debugging interfaces, and people with physical access to