Value and nullability analysis in C#

JetBrains Fleet can analyze values in several ways:

• By understanding the behavior of language constructs.

  In the example below, based on the fact that the parameter obj was explicitly checked for nullability, JetBrains Fleet reasonably supposes that the value of obj can be indeed 'null' and displays the corresponding warning:

  

• By relying on code annotation attributes ([CanBeNull], [NotNull], [ItemCanBeNull], [ItemNotNull]) when Nullable reference types are disabled.

  In the following example, the method Bar is marked with the [CanBeNull] attribute, Using this information, JetBrains Fleet warns you that the return value of Bar can be null, and calling a method on it could lead to a 'null' dereference:

  

  tip

  If necessary, you can make code analysis even more precise with contract annotations in c#. They help you define dependencies between arguments of a function and its return value.

• In C# 8.0 and later, JetBrains Fleet can reuse results of the compiler analysis if Nullable reference types are enabled in the project.

tip

You can instantly fix these problems (for example, automatically add a nullability check) using quick-fixes ( AltEnter).

JetBrains Fleet helps you analyze the use of the equality operators (== and !=) in the following ways:

• It reports equality comparison of floating point numbers.

• In addition to compiler warnings of 'Possible unintended reference comparison' (CS0252 and CS0253), it also reports cases when only one of the compared types overrides Equals().

• It provides the [CannotApplyEqualityOperator] attribute that helps detect unintended use of the equality operators for types that are designed to be compared using Equals().

If nullable reference types (NRT) are enabled, JetBrains Fleet reuses the results of C# compiler analysis.

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 (for example, Expression is always 'true' or 'false') . You can choose to ignore nullable API contracts and report a problem only when previous operations with the value in your code guarantee that it can or cannot be null.

Here are some more examples of JetBrains Fleet's value and nullability analysis:

• If a nullability check has been already done with a simple LINQ query, JetBrains Fleet tells you that a further nullability check is redundant:

  

• The same happens if you mark a collection with the [ItemNotNull] attribute: