CLion
 
2024.1
Shortcuts: Windows
Get CLion
You are viewing the documentation for an earlier version of CLion.
  1. Static code analysis
  2. Enable/disable and suppress inspections

Enable/disable and suppress inspections

Last modified: 26 May 2024

Some inspections may report problems that you currently do not want to see. In this case, you can disable or suppress them.

Disable inspections

When you disable an inspection, you turn it off. It means that the code analysis engine stops searching project files for the problem that this inspection is designed to detect. Note that when you disable an inspection, you disable it in the current inspection profile; it remains enabled in other profiles.

Most inspections in CLion can be disabled. However, some inspections will keep highlighting your code regardless of the settings. For example, syntax errors are always highlighted.

Disable an inspection in settings

  1. Press CtrlAlt0S to open settings and then select Editor | Inspections.

  2. Locate the inspection you want to disable, and clear the checkbox next to it.

    Enable inspection

  3. Apply the changes and close the dialog.

Disable an inspection from the editor

  1. Place the caret at the highlighted line and press AltEnter (or click the Intention action icon to use the intention action).

  2. Click the arrow next to the inspection you want to disable, and select Disable inspection.

    Disable an inspection in the editor

Disable an inspection from the Problems tool window

  1. In the Inspection Results tab of the Problems tool window (appears once you run code analysis), right-click the inspection you want to disable and select Disable inspection.

  2. Click the Filter resolved items icon to hide the disabled inspection alerts.

Suppress inspections

When you suppress an inspection, the code analysis engine doesn't highlight the problem found by this inspection in the specific piece of code (file, statement, function, or line) .

Most inspections in CLion can be suppressed. However, some inspections do not have this option. For example, syntax errors are always highlighted in the editor regardless of the settings.

Suppress an inspection from the editor

  1. Place the caret at the highlighted line and press AltEnter (or click the Intention action icon to use the intention action).

  2. Click the button next to the inspection you want to suppress and select the necessary suppress action.

    Suppress inspection in the editor

For C/C++ code, CLion uses the #pragma clang diagnostic to suppress inspections. For example, when you suppress one of the Clang-Tidy inspections, modernize-avoid-bind, for a selected function, the following code appears above and below the declaration:

Suppressing an inspection for a function

Clang-Tidy inspections have the additional Suppress for line option, which adds the // NOLINT comment, forcing Clang-Tidy to ignore the current line:

Suppressing an inspection for a lilne

To re-enable a suppressed inspection, delete the #pragma lines or // NOLINT comments.

Disable highlighting, but keep the fix

Inspections have severities according to which they highlight code problems in the editor. You can quickly disable code highlighting for an inspection without opening the settings. In this case, the inspection remains enabled and provides a fix, but the severity changes to No highlighting (fix available).

If you want to restore the highlighting, press CtrlAlt0S to open the IDE settings and select Editor | Inspections. Find the necessary inspection in the list and change its severity as you like. For more information, refer to Change inspection severity in all scopes.

Change the highlighting level for a file

See also

Procedures

Concepts