Code Inspection: Expression is always 'true' or always 'false'
This inspection is fairly obvious: ReSharper analyzes values and nullability of symbols and suggests to eliminate expressions that are always true or always false.
The only problem with this inspection is that sometimes it's not obvious how ReSharper has come to this conclusion. Because of this, users may be unwilling to accept the ReSharper’s suggestion to replace an expression with explicit true or false, or to remove a redundant check in an if statement. Below are some StackOverflow questions that illustrate this problem:
ReSharper claims that my expression is always true? Is it correct or is it a bug?
Trying to understand why resharper told me expression is always false