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

Improve wording

Browse Source
This commit is contained in:
Nilstrieb 2022-10-01 20:10:43 +02:00
parent b91dc03510
commit 169ef781f9
No known key found for this signature in database
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
clippy_lints/src/casts/mod.rs
View File

@ -602,8 +602,8 @@ declare_clippy_lint! {
/// Checks for the result of a `&self`-taking `as_ptr` being cast to a mutable pointer
///
/// ### Why is this bad?
/// Since `as_ptr` took a `&self`, the pointer won't have write permissions, making it
/// unlikely that having it as a mutable pointer is correct.
/// Since `as_ptr` takes a `&self`, the pointer won't have write permissions unless interior
/// mutability is used, making it unlikely that having it as a mutable pointer is correct.
///
/// ### Example
/// ```rust
@ -620,7 +620,7 @@ declare_clippy_lint! {
#[clippy::version = "1.66.0"]
pub AS_PTR_CAST_MUT,
nursery,
"casting the result of the `&self`-taking as_ptr to a mutabe point"
"casting the result of the `&self`-taking `as_ptr` to a mutabe pointer"
}
pub struct Casts {

4
src/docs/as_ptr_cast_mut.txt
View File

@ -2,8 +2,8 @@
Checks for the result of a `&self`-taking `as_ptr` being cast to a mutable pointer
### Why is this bad?
Since `as_ptr` took a `&self`, the pointer won't have write permissions, making it
unlikely that having it as a mutable pointer is correct.
Since `as_ptr` takes a `&self`, the pointer won't have write permissions unless interior
mutability is used, making it unlikely that having it as a mutable pointer is correct.
### Example
```