Error may be not nil
Reports instances where variables might have nil or an unexpected value because of the associated error that is not checked for being non-nil, as in v, err := foo().
The quick-fix removes the function from the scope of this inspection.
Example:
In the example provided, file could be nil or have an unexpected value if err is not nil.
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
GoDfaErrorMayBeNotNil- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
Inspection ID: GoDfaErrorMayBeNotNil
Inspection options
Here you can find the description of settings available for the Error may be not nil inspection, and the reference of their default values.
Exclude
- Import Path
Option ID:
excludedFunctions.myExcludedFunctions.myImportPathsDefault value:
None- Function Name
Option ID:
excludedFunctions.myExcludedFunctions.myFunctionNamesDefault value:
None
- Import Path
Option ID:
excludedFunctions.myExcludedMethods.myImportPathsDefault value:
None- Receiver
Option ID:
excludedFunctions.myExcludedMethods.myReceiversDefault value:
None- Method Name
Option ID:
excludedFunctions.myExcludedMethods.myMethodNamesDefault value:
None
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |