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
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Go

Go static code analysis

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

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
 
Tags
    Impact
      Clean code attribute
        1. All branches in a conditional structure should not have exactly the same implementation

           Bug
        2. Non-existent operators like "=+" should not be used

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

           Bug
        4. Identical expressions should not be used on both sides of a binary operator

           Bug
        5. All code should be reachable

           Bug
        6. Variables should not be self-assigned

           Bug
        7. Useless "if(true) {...}" and "if(false){...}" blocks should be removed

           Bug

        All branches in a conditional structure should not have exactly the same implementation

        intentionality - clear
        reliability
        Bug

          Why is this an issue?

          Having all branches of a switch or if chain with the same implementation indicates a problem.

          In the following code:

          if b == 0 {  // Noncompliant
            doOneMoreThing()
          } else {
            doOneMoreThing()
          }
          
          switch i {  // Noncompliant
            case 1:
              doSomething()
            case 2:
              doSomething()
            case 3:
              doSomething()
            default:
              doSomething()
          }
          

          Either there is a copy-paste error that needs fixing or an unnecessary switch or if chain that should be removed.

          Exceptions

          This rule does not apply to if chains without else, nor to switch without a default clause.

          if b == 0 {    //no issue, this could have been done on purpose to make the code more readable
            doSomething()
          } else if b == 1 {
            doSomething()
          }
          
            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 Community BuildAnalyze code in your
            on-premise CI
            Available Since
            9.1
          • 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