Spotting returns is valuable to avoid accidentally putting teardown logic after early conditional return
-
-
it's not "hard"; it's just the lost time that adds up. i spent a day this year trying to debug 5 levels of deps 1/2
-
i could've saved some time (hours) had some libs been a little friendlier to debugging 2/2
-
that's really just a 'worst case' scenario that most peeps won't encounter
-
can you explain the problemM
-
braceless can result in harder targets which results inure time; not meant to be a blanket statement, depends on the code
-
if (condition) return; doesn't suffer from that problem.
-
it can; your pref is pushed downstream and can add costs you don't expect for persons dealing with it
-
I respect the opinion, I used to share it, but I've learned from the costs
- 9 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.