4 ms·
Yeah I get that, that's always the argument. I'm not an absolutist on this either (I do sprinkle continue/return into my code once in a while when it really see
by dataflow 5y ago
Yeah I get that, that's always the argument. I'm not an absolutist on this either (I do sprinkle continue/return into my code once in a while when it really seems worth it; even the same with the occasional goto), but in general I feel people are way more liberal with these than they should be (except goto, which people avoid at all costs no matter how complicated the code becomes, thus erring toward the other extreme). Never been able to convince many others though; the arguments never get anywhere when person A insists X is more readable and person B insists Y is more readable.
- jraph 5y agoAt the end, readability depends heavily on habits. You can know that, but you feel it when you work on various codebases with different people / switch teams. So, yes. Nobody is right or wrong in these topics. Moreover, there are situations where one is clearly better than the other. If you need to (formally) verify your code, depending on the method, maybe early returns are to be avoided.
- avar 5y agoThe use of "goto" is fine and more legible in some contexts, such as jumping to the "cleanup" part of a function. You can avoid it, but it'll involve one of repetition, a wrapper function, or "formalizing" the cleanup so that it's your only cleanup call. Depending on the situation those are all going to be way more verbose. Some advanced use cases include jumping between "case" labels, or jumping into the middle of a loop. Most of the time that's bad practice, but in the cases that benefit from them it's much better than the alternatives.