Can you showcase some example code that triggers this behavior?

Are some_value and another_value the same constant value? (Also is there a chance that the values of some_value and another_value` are build dependent?)

To add more context, we have internal bug(http://b/198584074) asking to make warnings more descriptive.

Analysis warning would be triggered by of expressions of type:

e && e // the same as e
e || e // the same as e
x != c1 || x != c2 // always true
x == c1 && x == c2 // always false

Where x is variable; c1, c2 are constants and c1 != c2

I also created CL to change this: http://go.dev/cl/507675

If someone can suggest a sufficiently terse that is correct warning message that is clearer, I think it is fine to change the error message for this case.