LowFile-scopeDart Plug & play

Remove Unused Assignments

Eliminate assignments to variables that are never used or overwritten immediately to improve code efficiency and readability.

Why this matters

Assignments to variables that are never used waste computation and clutter the code. Remove them to improve clarity.

Side-by-side examples engineers can pattern-match during review.

Avoid

int foo(int y) {
  int x = 100; // Noncompliant: dead store
  x = 150;     // Noncompliant: dead store
  x = 200;
  return x + y;
}

Prefer

int foo(int y) {
  int x = 200; // Compliant: no unnecessary assignment
  return x + y;
}

Bad

int foo(int y) {
  int x = 100; // Noncompliant: dead store
  x = 150;     // Noncompliant: dead store
  x = 200;
  return x + y;
}

Good

int foo(int y) {
  int x = 200; // Compliant: no unnecessary assignment
  return x + y;
}

From the same buckets as this rule.

Critical
Avoid Duplicating String Literals
Store repeated string literals in constants or variables to improve maintainability and reduce redundancy.
duplication-complexitymaintainability
Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
Critical
Avoid modifying built-in prototypes
Detect modifications to built-in prototypes. Modifying built-in objects can lead to compatibility issues and unexpected behavior. Recommend creating helper functions instead.
maintainabilitysecurity-hardening