Code inspection: A suppressed nullable warning might hide an underlying problem

This inspection reports use of the null-forgiving operator (!) when it hides a nullable warning instead of fixing the underlying nullability problem. It is a hint that the code is relying on an assumption that might no longer be true after refactoring or API changes.

Example

                string GetName(User? user)
                {
                    return user!.Name;
                }
            

                string GetName(User? user)
                {
                    if (user is null)
                        throw new ArgumentNullException(nameof(user));
                    return user.Name;
                }
            

How to fix

This inspection does not have a dedicated code quick-fix. The usual fix is to add a real null check, adjust the flow so the value is known to be non-null, or change the API nullability if the value really cannot be null.

01 April 2026