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
Filtered: 4 rules found
clumsy
    Impact
      Clean code attribute
        1. Mathematical constants should not be hardcoded

           Code Smell
        2. Erasing mathematical operations should not be performed

           Code Smell
        3. "to_string()" should never be called on a String value

           Code Smell
        4. Local variables should not be declared and then immediately returned

           Code Smell

        "to_string()" should never be called on a String value

        intentionality - clear
        maintainability
        Code Smell
        • finding
        • clumsy
        • clippy

        Why is this an issue?

        More Info

        Calling the to_string method on a value that is already of type String in Rust is redundant and unnecessary. This redundant call does not change the value and only adds unnecessary complexity to the code. It can also be confusing to readers and may lead to misunderstandings about the code’s intent.

        If the intent was to clone the string, it is better to use the clone method instead.

        Avoiding such redundant calls helps keep the code clean, concise, and more readable.

        Noncompliant code example

        let message = String::from("hello world");
        println!("{}", message.to_string()); // Noncompliant: 'message' is already a String
        

        Compliant solution

        let message = String::from("hello world");
        println!("{}", message);
        
        // or
        
        let cloned_message = message.clone(); // Use 'clone' if you need a duplicate
        println!("{}", cloned_message);
        
          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