Lint nonminimal-bool: suggests current code

[mvuets]

I've run into a boolean expression that Clippy marks as clippy::nonminimal-bool, however the suggested rewrite is exactly the same as the current code. Seems like a minor false positive bug to me.

Minimal reproducible example:

fn main() {
    let (d1, d2, d3) = (2, 4, 4);
    let _f = d1 == d2 && d2 != d3 || d1 != d2 && d2 == d3;
}

Clippy output:

$ cargo clippy -- -D clippy::nonminimal-bool
    Checking nonminbool v0.1.0 (/home/mvuets/tmp/nonminbool)
error: this boolean expression can be simplified
 --> src/main.rs:3:14
  |
3 |     let _f = d1 == d2 && d2 != d3 || d1 != d2 && d2 == d3;
  |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `d1 == d2 && d2 != d3 || d1 != d2 && d2 == d3`
  |
  = note: requested on the command line with `-D clippy::nonminimal-bool`
  = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#nonminimal_bool
# -- snip --

FWIW, the lint description mentions "ignores short circuiting behavior" as a known problem, however I believe that's not the case here.

clippy --version: clippy 0.0.212 (4e7e71b 2019-10-11)

[ghost]

Is this equivalent to let _f = (d1 == d2) ^ (d2 == d3)? 🤔

[flip1995]

cc #4548

and @mikerite fixed this already in #4568. At least it doesn't trigger on the Playground