TL;DR: Don't Assign and overwrite values
Remove the sentences that have no effect.
The "dead store" code smell refers to a situation in programming where a variable is assigned a value but is never subsequently read or used in the program. It's a variable that is given a value but that value is never utilized, making the assignment unnecessary and potentially indicative of a mistake or inefficiency in the code.
This code smell can arise for various reasons, including during refactoring or changes in the program logic over time. Unused variables may clutter the code, making it harder to understand and potentially impacting performance.
<?
$lastGoalAuthor = "Lio Messi";
$lastGoalAuthor = "Ángel Di María";
$lastGoalAuthor = "Lio Messi";
// This is stored unconditionally
// You can optimize it by removing the first two statements
// Since storing in a variable has no side effects
<?
$lastGoalAuthor = "Lio Messi";
// If you want to keep the last one
$goalAuthors[] = "Lio Messi";
$goalAuthors[] = "Ángel Di María";
$goalAuthors[] = "Lio Messi";
// If you want to keep a list
$lastGoalAuthor = firstGoalAutor();
$lastGoalAuthor = secondGoalAutor();
$lastGoalAuthor = thirdGoalAutor();
// This might be valid since functions in
// Object-Oriented Programming might have side effects
// and you cannot remove the first ones
// Unless you ensure they don't have side effects
Several linters can find this problem using ASTs
Code generated by AIs usually doesn't have this problem.
Avoiding dead store code helps improve code quality, maintainability, and resource efficiency.
It contributes to a more understandable, robust, and bug-free codebase. Regular code reviews, static analysis tools, and good programming practices can aid in identifying and addressing dead store code smells.
Disclaimer: Code Smells are my opinion.
Photo by Brayan Becerra on Unsplash
Good programmers use their brains, but good guidelines save us having to think out every case.
This article is part of the CodeSmell Series—How to Find the Stinky Parts of your Code