Code Inspection: Expression is always 'true' or 'false' according to nullable reference types' annotations
This inspection woks in C# 8.0 and later when nullable reference types (NRT) are enabled, and reports expressions that are always
true or always
false based on the NRT contracts.
NRT improve overall precision of the nullability analysis, but there are cases when NRT contracts can be violated, for example when values are coming from code without
#nullable context. In such cases you may get false positive warnings for nullability checks . In such cases, you can choose to ignore nullable API contracts and only report such cases when previous operations with the value in your code guarantee that it can or cannot be null.
You can change this behavior right from the Alt+Enter menu:
... or using the Nullable reference types' warnings mode option on the page of ReSharper options .
When ReSharper ignores nullable API contracts, nullability analysis relies on the program control flow to report redundant null checks. It will use another inspection for that. For example:
To learn more about NRT and how ReSharper supports them, watch this webinar recording: