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

        Mathematical constants should not be hardcoded

        intentionality - clear
        maintainability
        Code Smell
        • clippy
        • clumsy

        Why is this an issue?

        More Info

        Floating-point literals that approximate constants defined in std::f32::consts or std::f64::consts should be replaced with the predefined constants. Using the standard library constants ensures higher precision and avoids potential rounding errors that can occur when manually approximating these values. It also improves code readability and maintainability, as it clearly indicates the intended constant value.

        Noncompliant code example

        let x = 3.14; // Noncompliant: Approximates PI
        let y = 1_f64 / 3.1415926535; // Noncompliant: Approximates FRAC_1_PI
        

        Compliant solution

        use std::f32::consts::PI;
        use std::f64::consts::FRAC_1_PI;
        
        let x = PI; // Compliant: Uses the predefined PI constant
        let y = FRAC_1_PI; // Compliant: Uses the predefined FRAC_1_PI constant
        
          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