SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C++

C++ static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C++ code

  • All rules 798
  • Vulnerability14
  • Bug173
  • Security Hotspot19
  • Code Smell592

  • Quick Fix 99
Filtered: 35 rules found
unused
    Impact
      Clean code attribute
        1. Non-empty statements should change control flow or have at least one side-effect

           Bug
        2. Unused type declarations should be removed

           Code Smell
        3. Calls to "std::format" with a locale should use the "L" flag

           Code Smell
        4. "std::format" should not have unused arguments

           Code Smell
        5. "std::format" should not be missing indexes

           Bug
        6. Width, alignment, and padding format options should be used consistently

           Code Smell
        7. Functions that are not used in a project should be removed

           Code Smell
        8. "extern" shouldn't be used on member definitions

           Bug
        9. Reference types should not be qualified with "const" or "volatile"

           Code Smell
        10. Namespaces should not be empty

           Code Smell
        11. Forward declarations should not be redundant

           Code Smell
        12. Declarations should not be empty

           Code Smell
        13. "catch" clauses should do more than rethrow

           Code Smell
        14. Conditionally executed code should be reachable

           Bug
        15. Values should not be uselessly incremented

           Bug
        16. Related "if/else if" statements should not have the same condition

           Bug
        17. Unused assignments should be removed

           Code Smell
        18. All code should be reachable

           Bug
        19. Unused local variables should be removed

           Code Smell
        20. Sections of code should not be commented out

           Code Smell
        21. Unused function parameters should be removed

           Code Smell
        22. Unused functions and methods should be removed

           Code Smell
        23. Empty statements should be removed

           Code Smell
        24. Unused "private" fields should be removed

           Code Smell
        25. Unused labels should be removed

           Code Smell
        26. Condition-specific "catch" handlers should not be used after the ellipsis (catch-all) handler

           Bug
        27. Functions with "limited visibility" should be "used" at least once

           Code Smell
        28. Sections of code should not be "commented out"

           Code Smell
        29. A named function parameter shall be "used" at least once

           Code Smell
        30. The value returned by a function shall be "used"

           Code Smell
        31. A value should not be "unnecessarily written" to a local object

           Code Smell
        32. Types with "limited visibility" should be "used" at least once

           Code Smell
        33. Variables with "limited visibility" should be "used" at least once

           Code Smell
        34. Controlling expressions should not be invariant

           Bug
        35. A function shall not contain "unreachable" statements

           Bug

        A named function parameter shall be "used" at least once

        intentionality - clear
        maintainability
        Code Smell
        • unused
        • misra-c++2023
        • misra-required

        Why is this an issue?

        More Info

        This rule is part of MISRA C++:2023.

        Usage of this content is governed by Sonar’s terms and conditions. Redistribution is prohibited.

        Rule 0.2.2 - A named function parameter shall be used [1] at least once

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Amplification

        This rule does not apply to parameters that are declared [[maybe_unused]].

        Note: this rule also applies to the parameters of a lambda.

        Rationale

        It is expected that most functions will use [1] their parameters. If a function parameter is unused [2], it is possible that the implementation of the function may not satisfy its requirements. This rule helps to highlight such potential mismatches.

        In cases where an unused [2] parameter is required, for example when defining a virtual function or a callback [3] function, the parameter can be left unnamed. Where the use of a parameter depends on the expansion of a macro or varies between different template instantiations, then the parameter can be declared [[maybe_unused]].

        Example

        class B
        {
        public:
          virtual int16_t f( int16_t a, int16_t b );
        };
        
        class D1 : public B
        {
        public:
          int16_t f( int16_t a, int16_t b ) override         // Non-compliant - 'b' unused
          {
            return a;
          }
        };
        
        class D2 : public B
        {
        public:
          int16_t f( int16_t a,                  // Compliant - 'a' is used
                     int16_t ) override          // Rule does not apply - unnamed parameter
          {
            return a;
          }
        };
        
        class D3 : public B
        {
        public:
          int16_t f( int16_t a, int16_t b ) override         // Compliant
          {
            return a + b;
          }
        };
        
        class D4 : public B
        {
        public:
          int16_t f( int16_t a,                              // Compliant
                     int16_t b [[maybe_unused]] ) override   // Rule does not apply -
                                                             //   declared [[maybe_unused]]
          {
            assert( b > 0 );                     // assert macro may expand to nothing,
                                                 // leaving 'b' unused.
            return a;
          }
        };
        
        void f1(int32_t i,                       // Non-Compliant
                int32_t j )                      // Compliant - explicitly cast to void
        {
          ( void )j;
        
          auto l = []( int32_t m,                // Compliant
                       int32_t n )               // Non-compliant
          {
            return m;
          };
        }
        
        template< bool b >
        int32_t f2( int32_t i,                   // Non-compliant for f2< false >
                    int32_t j [[maybe_unused]] ) // Rule does not apply - [[maybe_unused]]
        {
          if constexpr ( b )
          {
            return i + j;
          }
        
          return 0;
        }
        

        Glossary

        [1] Use / used / using

        An object is used if:

        • It is the subject of a cast; or
        • It is explicitly initialized at declaration time; or
        • It is an operand in an expression; or
        • It is referenced.

        A function is used as defined in M23_331: MISRA C++ 2023 Rule 0.2.4.

        A type is used as defined in M23_005: MISRA C++ 2023 Rule 0.2.3.

        [2] Unused

        An entity is unused if it is not used [1].

        [3] Callback

        A callback is a function that is called indirectly via a function pointer or a handle.

        Copyright The MISRA Consortium Limited © 2023

          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use