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
Rust

Rust static code analysis

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

  • All rules 85
  • Bug60
  • Code Smell25

  • Quick Fix 4
 
Tags
    Impact
      Clean code attribute
        1. Clamping values with `cmp::min` and `cmp::max` should use correct ranges

           Bug
        2. Redundant casts should be avoided

           Code Smell
        3. Field init shorthand should be used

           Code Smell
        4. Closures should be replaced with function pointers

           Code Smell

        Field init shorthand should be used

        consistency - conventional
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarQube for IDE
        • clippy

        Why is this an issue?

        More Info

        In Rust, field init shorthand syntax is a more concise way to define fields in structs. It was introduced to make struct initialization more readable and expressive.

        In the shorthand syntax, if a variable exists in the scope with the same name as the struct field you’re defining, you can omit the field name and just write the variable name. The compiler will automatically understand that the field and the variable are linked.

        Using field init shorthand syntax can make your code cleaner and easier to read. It can also reduce the chance of making errors, as you don’t have to repeat yourself by writing the variable name twice.

        let a = 1;
        
        struct MyStruct {
          a: i32,
        }
        
        let my_struct = MyStruct {
          a: a,  // Noncompliant
        };
        

        You can omit the field name and the colon if it is the same as the local variable name.

        let a = 1;
        
        struct MyStruct {
          a: i32,
        }
        
        let my_struct = MyStruct {
          a,
        };
        
          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use