<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Mar 23, 2018, at 12:41 PM, Brian Goetz <<a href="mailto:Brian.Goetz@Oracle.COM" class="">Brian.Goetz@Oracle.COM</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I think so. Its not detecting the ambiguity, its that the possibility of mixing control flow kinds means the poor reader has to reason about all the possibilities, and not be sure what "break FOO" means in a switch statement.</span></div></blockquote></div><br class=""><div class="">A lighter fix, then, would be to require parentheses always.</div><div class="">An even lighter fix would be leave that kind of clarification to style guides.</div><div class=""><br class=""></div></body></html>