Skip to content

Commit

Permalink
Auto merge of rust-lang#6794 - camsteffen:needless-borrowed-ref, r=fl…
Browse files Browse the repository at this point in the history
…ip1995

Improve needless_borrowed_ref docs

changelog: none

I think "borrowed ref" is a confusing description for this lint. Destructuring a reference is the opposite of borrowing. So I updated the wording throughout the docs. Unfortunately this nit applies to the name of the lint itself, but I won't bother changing that. One motivation for these changes is to clarify the difference between this lint and `needless_borrow` (they are actually quite different). Let me know if I need to clarify anything or if you disagree with any changes.
  • Loading branch information
bors committed Mar 10, 2021
2 parents fb27517 + 5dbd45c commit a1e25a9
Showing 1 changed file with 18 additions and 29 deletions.
47 changes: 18 additions & 29 deletions clippy_lints/src/needless_borrowed_ref.rs
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
//! Checks for useless borrowed references.
//!
//! This lint is **warn** by default
use crate::utils::{snippet_with_applicability, span_lint_and_then};
use if_chain::if_chain;
use rustc_errors::Applicability;
Expand All @@ -10,44 +6,37 @@ use rustc_lint::{LateContext, LateLintPass};
use rustc_session::{declare_lint_pass, declare_tool_lint};

declare_clippy_lint! {
/// **What it does:** Checks for useless borrowed references.
///
/// **Why is this bad?** It is mostly useless and make the code look more
/// complex than it
/// actually is.
/// **What it does:** Checks for bindings that destructure a reference and borrow the inner
/// value with `&ref`.
///
/// **Known problems:** It seems that the `&ref` pattern is sometimes useful.
/// For instance in the following snippet:
/// ```rust,ignore
/// enum Animal {
/// Cat(u64),
/// Dog(u64),
/// }
/// **Why is this bad?** This pattern has no effect in almost all cases.
///
/// fn foo(a: &Animal, b: &Animal) {
/// **Known problems:** In some cases, `&ref` is needed to avoid a lifetime mismatch error.
/// Example:
/// ```rust
/// fn foo(a: &Option<String>, b: &Option<String>) {
/// match (a, b) {
/// (&Animal::Cat(v), k) | (k, &Animal::Cat(v)) => (), // lifetime mismatch error
/// (&Animal::Dog(ref c), &Animal::Dog(_)) => ()
/// }
/// (None, &ref c) | (&ref c, None) => (),
/// (&Some(ref c), _) => (),
/// };
/// }
/// ```
/// There is a lifetime mismatch error for `k` (indeed a and b have distinct
/// lifetime).
/// This can be fixed by using the `&ref` pattern.
/// However, the code can also be fixed by much cleaner ways
///
/// **Example:**
/// Bad:
/// ```rust
/// let mut v = Vec::<String>::new();
/// let _ = v.iter_mut().filter(|&ref a| a.is_empty());
/// ```
/// This closure takes a reference on something that has been matched as a
/// reference and
/// de-referenced.
/// As such, it could just be |a| a.is_empty()
///
/// Good:
/// ```rust
/// let mut v = Vec::<String>::new();
/// let _ = v.iter_mut().filter(|a| a.is_empty());
/// ```
pub NEEDLESS_BORROWED_REFERENCE,
complexity,
"taking a needless borrowed reference"
"destructuring a reference and borrowing the inner value"
}

declare_lint_pass!(NeedlessBorrowedRef => [NEEDLESS_BORROWED_REFERENCE]);
Expand Down

0 comments on commit a1e25a9

Please sign in to comment.