From 0df002a2e2001bf87f56d27ebf300daa4b574b6b Mon Sep 17 00:00:00 2001 From: Marc Schoolderman Date: Tue, 29 Aug 2023 11:20:56 +0200 Subject: [PATCH] rewording after comments by @thomcc --- library/std/src/fs.rs | 10 +++++----- 1 file 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 ///