about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMarc Schoolderman <marc@tweedegolf.com>2023-08-29 11:20:56 +0200
committerMarc Schoolderman <marc@tweedegolf.com>2023-08-29 11:24:48 +0200
commit0df002a2e2001bf87f56d27ebf300daa4b574b6b (patch)
treeee337a70f257a5c8b4cce2fdab081d0685db66f3
parent53469cfc3f0cc25530c1b5407f5dad97f103f8c6 (diff)
downloadrust-0df002a2e2001bf87f56d27ebf300daa4b574b6b.tar.gz
rust-0df002a2e2001bf87f56d27ebf300daa4b574b6b.zip
rewording after comments by @thomcc
-rw-r--r--library/std/src/fs.rs10
1 files changed, 5 insertions, 5 deletions
diff --git a/library/std/src/fs.rs b/library/std/src/fs.rs
index 342ea156231..e506b321c25 100644
--- a/library/std/src/fs.rs
+++ b/library/std/src/fs.rs
@@ -1406,11 +1406,11 @@ impl Permissions {
     /// On Unix-based platforms this checks if *any* of the owner, group or others
     /// write permission bits are set. It does not check if the current
     /// user is in the file's assigned group. It also does not check ACLs.
-    /// Therefore even if this returns false you may not be able to write to the
-    /// file, and vice versa. The [`PermissionsExt`] trait gives direct access
-    /// to the permission bits but also does not read ACLs. If you need to
-    /// accurately know whether or not a file is writable use the `access()`
-    /// function from libc.
+    /// Therefore the return value of this function cannot be relied upon
+    /// to predict whether attempts to read or write the file will actually succeed.
+    /// The [`PermissionsExt`] trait gives direct access to the permission bits but
+    /// also does not read ACLs. If you need to accurately know whether or not a file
+    /// is writable use the `access()` function from libc.
     ///
     /// [`PermissionsExt`]: crate::os::unix::fs::PermissionsExt
     ///