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 674
  • Vulnerability13
  • Bug139
  • Security Hotspot19
  • Code Smell503

  • Quick Fix 91
Filtered: 29 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. The value returned by a function shall be "used"

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

           Code Smell

        The value returned by a function shall be "used"

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

        Why is this an issue?

        More Info

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

        MISRA Rule 0.1.2

        Category: Required

        Analysis Type: Decidable,Single Translation Unit

        Amplification

        This rule only applies when the function is called explicitly using function call syntax.

        Rationale

        It is possible to call a function without using [1] the return value, which may be an error. If the return value of a function is intended to be explicitly discarded, it should be cast to void to ensure that it is used [1].

        Overloaded operators are excluded from this requirement, as they should behave in the same way as built-in operators.

        Note: this rule effectively requires all non-void functions to be treated as if they were declared [[nodiscard]].

        Example

        uint16_t func();
        
        void discarded()
        {
          func();                         // Non-compliant - implicitly discarded
          ( void )func();                 // Compliant - void cast is a use
          auto b = func();                // Compliant - used as initializer
        }
        
        void f1( std::string q )
        {
          std::string s { q } ;           // Rule does not apply - not function call syntax
          s = q;                          // Rule does not apply - not function call syntax
          s.operator=( q );               // Non-compliant
        }
        
        void f2( std::function< int() > & f )
        {
          f();                            // Non-compliant - using function call syntax
        
          auto a = []() { return 10; };
          a();                            // Non-compliant - using function call syntax
        }
        

        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 MISRA C++ 2023 Rule 0.2.3 (Types with limited visibility should be used at least once).

        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

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use