Timeline for Does it make sense to create blocks just to reduce a variable's scope?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2018 at 21:38 | comment | added | doubleOrt | @candied_orange Oh, thought you were arguing and not extending RubberDuck's argument. | |
| Jul 10, 2018 at 21:12 | comment | added | candied_orange | @doubleOrt I meant intermediate refactoring steps are real and necessary but certainly don't need to be enshrined in source control where everyone can look at it. Just finish refactoring before you check in. | |
| Jul 10, 2018 at 20:27 | comment | added | doubleOrt | @candied_orange I fear I get it not :( Care to elaborate ? | |
| Nov 30, 2017 at 1:51 | comment | added | candied_orange | @RubberDuck true, but in that case the rest of us should never see it so it doesn't matter what we think. What an adult coder and an a consenting compiler get up to in the privacy of their own cubicle is no one else's concern. | |
| Nov 29, 2017 at 22:00 | comment | added | RubberDuck | I think your answer skirts by a key usecase, it’s an intermediate step during a refactor. It can be useful to limit the scope and know your code still works just prior to extracting a method. | |
| Nov 29, 2017 at 15:37 | review | First posts | |||
| Nov 29, 2017 at 18:19 | |||||
| Nov 29, 2017 at 15:33 | history | answered | Casey Langford | CC BY-SA 3.0 |