mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Reword a question into a statement.

Browse Source
This commit is contained in:
Dan Gohman 2022-06-08 08:24:28 -07:00
parent f9662f2c18
commit 7656e085e3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
library/std/src/os/unix/io/mod.rs
View File

@ -52,8 +52,8 @@
//! and writes happen outside the control of the Rust compiler, so they do not //! and writes happen outside the control of the Rust compiler, so they do not
//! uphold Rust's memory safety guarantees. //! uphold Rust's memory safety guarantees.
//! //!
//! Does this mean that all APIs that might allow `/proc/self/mem` to be opened //! However, this does not mean that all APIs that might allow `/proc/self/mem`
//! and read from or written to must be `unsafe`? No. Rust's safety guarantees //! 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 //! 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 //! 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 //! external entity, along with debugging interfaces, and people with physical access to