I very much enjoyed the discussion, I'm sorry if it got heated. In any case, I think single-exit is fine for a corporation that needs to use clearly-defined, e

I very much enjoyed the discussion, I'm sorry if it got heated. In any case, I think single-exit is fine for a corporation that needs to use clearly-defined, easy-to-follow policies. It's a reasonable baseline. However, there are cases where trying to workaround multiple exits does lead to more errors. A function that returns 'right' 'left' or 'both' is probably better off having 3 returns rather than assigning the result to a local variable and carrying it to the end of the function. You might declare the local as the wrong type, you might forget an 'else' and accidentally overwrite the return value, etc. "No early exits unless your function has no side-effects" is a lot less clear to most programmers. Of those 495 bugs on the bug list, how many were caused by broken side-effects?