remove-single-use-functions

To safely remove single-use functions during code refactoring, identify local non-exported functions used exactly once, then inline their logic directly into the calling code to preserve behavior, types, and style.

You should inline a helper function to clean up your codebase when it is a local, non-exported function used only once, eliminating unnecessary code complexity while maintaining the original program functionality.

The best way to eliminate redundant helper functions without altering functionality is to inline the single-use function's logic into its caller, preserving the original behavior, types, and coding style throughout the refactoring process.

No, this refactoring approach targets local, non-exported functions used exactly once. Exported functions may be part of a public API and cannot be safely removed without checking for external usage.

Single-use function removal is suitable for small-scale cleanup tasks and code reviews. Large-scale refactoring may require broader analysis to ensure removing functions does not impact overall codebase maintainability.