ReSharper 2016.3 Help

Code Inspection: Nullable attribute usage with declaration having value or void type

In the code snippet below, the NotNull annotation is meaningless.

public void SetAge([NotNull] int age) { myAge = age; }
Public Sub SetAge(<NotNull> age As Integer) myAge = age End Sub

The reason is that int cannot possibly be null, so any sort of indication that it is or is not null is redundant and can be removed. The same applies to methods that have a void return type.

See Also

Last modified: 3 April 2017