<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 26, 2016, at 6:12 PM, Zachary Turner via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Back to the formatting issue, there's a lot of code that's going to look bad after the reformat, because we have some DEEPLY indented code. LLVM has adopted the early return model for this reason. A huge amount of our deeply nested code could be solved by using early returns. </div></div></blockquote><div><br class=""></div><div>FWIW, early returns are part of the LLVM Coding standard:</div><div><a href="http://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code" class="">http://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code</a></div><div><br class=""></div><div>So it makes sense for LLDB to adopt this approach at some point.</div><div><br class=""></div><div>I don’t have an opinion about whether it happens before or after the "big reformat", but I guess I agree with your point that doing it would be good to do it for the most egregious cases before the reformat.</div><div><br class=""></div><div>-Chris</div></div></body></html>