|
|
|
|
|
by denton-scratch
1615 days ago
|
|
Manual refactoring is certainly risky. So it should be set about with automated tests, specifically to protect the refactored functionality. But I think any legitimate refacvtoring can be carried out by automatic tools, with guarantees of unchanged functionality/semantics. The number of refactorings possible for any piece of code is almost infinite; you can't just let some tool loose on your code to perform all possible refactorings. That's madness. You need a human to judge which refactorings are beneficial. But the actual transformation should be performed by a tool that knows the language, and can guarantee semantic equivalence. And you still need tests. You can scrap them once the refactoring has been shown to have not changed the functionality. |
|