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: 5 rules found
since-c++14
    Impact
      Clean code attribute
        1. Transparent function objects should be used with associative "std::string" containers

           Code Smell
        2. Heterogeneous sorted containers should only be used with types that support heterogeneous comparison

           Bug
        3. The "_t" and "_v" version of type traits should be used instead of "::type" and "::value"

           Code Smell
        4. Standard groupings should be used with digit separators

           Code Smell
        5. Digit separators should be used

           Code Smell

        The "_t" and "_v" version of type traits should be used instead of "::type" and "::value"

        intentionality - clear
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarQube for IDE
        • since-c++14
        • clumsy

        Why is this an issue?

        When they were first introduced in the language, type traits, defined in header <type_traits>, required to use nested types (with ::type) or nested values (with ::value) to access the result of the trait. Since then, the language introduced templated alias declaration and variable templates that allow to define traits in a more direct and readable way.

        Even if the old variant still exists, the new one, which uses _t (C++14) and _v (C++17) suffixes as discriminant, should be preferred.

        Noncompliant code example

        template<class T>
        void f(T t) {
          static_assert (std::is_arithmetic<T>::value); // Noncompliant
          using rawType = std::remove_cv<T>::type; // Noncompliant
        }
        

        Compliant solution

        template<class T>
        void f(T t) {
          static_assert (std::is_arithmetic_v<T>); // Compliant, C++17
          using rawType = std::remove_cv_t<T>; // Compliant, C++14
        }
        
          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
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use