False postive for `if-let-rescope` on `hashbrown::HashMap::get`?

[Imberflur]

hashbrown::HashMap::get returns a reference which has no significant drop.

I've see this on other methods like hashbrown::HashMap::get_mut, the equivalent methods on std::collections::HashMap don't seem to have this false positive.

Code

#![warn(if_let_rescope)]
#![allow(unused_variables)]

fn main() {
    let h = hashbrown::HashMap::<u32, u32>::default();
    if let Some(value) = h.get(&0) {
        // do something
    } else {
        // do something else
    }
}

Code in the playground.

Current output

warning: `if let` assigns a shorter lifetime since Edition 2024
 --> src/main.rs:6:8
  |
6 |     if let Some(value) = h.get(&0) {
  |        ^^^^^^^^^^^^^^^^^^-^^^^^^^^
  |                          |
  |                          this value has a significant drop implementation which may observe a major change in drop order and requires your discretion
  |
  = warning: this changes meaning in Rust 2024
  = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/temporary-if-let-scope.html>
help: the value is now dropped here in Edition 2024
 --> src/main.rs:8:5
  |
8 |     } else {
  |     ^
note: the lint level is defined here
 --> src/main.rs:1:9
  |
1 | #![warn(if_let_rescope)]
  |         ^^^^^^^^^^^^^^
help: a `match` with a single arm can preserve the drop order up to Edition 2021
  |
6 ~     match h.get(&0) { Some(value) => {
7 |         // do something
8 ~     } _ => {
9 |         // do something else
10~     }}
  |

[Imberflur]

Another case with Arc::get_mut.
Seems to only occur when the contained type implements Drop.

#![warn(if_let_rescope)]
#![allow(unused_variables)]
use std::sync::Arc;

pub struct Droppy;
impl Drop for Droppy {
    fn drop(&mut self) {}
}

pub struct Foo {
    field: Arc<Droppy>,
}
impl Foo {
    // Triggers lint
    pub fn foo(&mut self) {
        if let Some(value) = Arc::get_mut(&mut self.field) {
            // do something
        } else {
            // do something else
        }
    }
}

// Triggers lint
pub fn foo1(mut arc: Arc<Droppy>) {
    if let Some(value) = Arc::get_mut(&mut arc) {
        // do something
    } else {
        // do something else
    }
}

/// Does NOT trigger lint
pub fn foo2(arc: &mut Arc<Droppy>) {
    if let Some(value) = Arc::get_mut(arc) {
        // do something
    } else {
        // do something else
    }
}

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=cc979cdabe0e185c6b3464c26aadbebd

[GnomedDev]

It seems like this doesn't even need Arc/HashMap, although this might be a separate issue:

#![warn(if_let_rescope)]
#![allow(unused_variables, clippy::needless_else)]

pub struct SigDrop;
impl Drop for SigDrop {
    fn drop(&mut self) {}
}

pub fn with_option() {
    let sigdrop = Some(SigDrop);
    if let Some(sigdrop_ref) = &sigdrop { // Triggers here
    } else {
    }
}

#[allow(irrefutable_let_patterns)]
pub fn irrefutable_pattern() {
    let sigdrop = SigDrop;
    if let sigdrop_ref = &sigdrop { // Triggers here
    } else {
    }
}

https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=19b83a57725cb634d73a36a7ae5aad25

This ends up triggering all over the https://github.com/serenity-rs/serenity codebase, making it hard to find a true positive.

[traviscross]

Closing in favor of:

• false positive for if-let-rescope on enums when the pattern exhaustively matches all cases with significant-drop fields #137376

[GnomedDev]

Is this a duplicate of that? My irrefutable_pattern repro doesn't require enums at all? @traviscross

[theemathas]

I don't think this is a duplicate. In this case, the value being rescoped doesn't even implement Drop. The other issue is about the lint not being able to reason that dropping None is a no-op.

[theemathas]

Another reproducer, which probably more clearly shows the cause of the issue:

#![warn(if_let_rescope)]

pub struct SigDrop;
impl Drop for SigDrop {
    fn drop(&mut self) {}
}

#[allow(irrefutable_let_patterns, dropping_references)]
pub fn irrefutable_pattern() {
    let sigdrop = SigDrop;
    if let () = drop(&sigdrop) { // Triggers here
    } else {
    }
}

It seems that merely creating a reference to a value that implements drop is enough to trigger the lint. In the hashmap example, it's presumably due to creating a reference to the hashmap itself. I don't know why the lint doesn't fire for the std hashmap though. (Maybe it's a may_dangle somewhere?)