clippy 0.1.92 (f04e3dfc87 2025-10-19) Weird Linting highlights VSC LSP

Summary

A redundant else{} block caused clippy to highlight TO THE END OF THE FILE. Link to folder with two screen recordings and image The first video shows me recreating the issue. The later one shows me trying to find varients of the issue, where at 0:20 the issue seems to reverse itself and it will only do the incorrect-highlight when I remove the redundant else{} block (not shown in the video). When it disappeared, however, It moved to another file (or more specifically the first open file in that tablist in VSC) as seen in the image

Reproducer

Actually, this was pretty simple:

use std::collections::HashSet;

fn main() {
    let _x = do_something();
    println!("Hello, world!");
}
fn do_something() -> HashSet<bool> {
    let bug = dbg!(
        [Some(true), None, Some(false)]
            .into_iter()
            .flatten()
            .collect::<HashSet<bool>>()
    ) else {
        println!("Failed to reproduce bug");
        return HashSet::new();
    };
    bug
}
fn do_something_else() {
    println!("WOrking...");
}

Version

rustc 1.92.0-nightly (f04e3dfc8 2025-10-19)
binary: rustc
commit-hash: f04e3dfc87d7e2b6ad53e7a52253812cd62eba50
commit-date: 2025-10-19
host: x86_64-unknown-linux-gnu
release: 1.92.0-nightly
LLVM version: 21.1.3

Additional Labels

No response

Start by running the supplied Rust reproducer with rustc 1.92.0-nightly in the reported VS Code LSP setup, then compare the diagnostic highlight with the source span. The issue is done when the redundant else variation no longer highlights to the end of the file or another open file, while the actual lint remains correctly highlighted.