<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 Dec 4, 2015, at 2:20 PM, Ray Fix <<a href="mailto:rayfix@gmail.com" class="">rayfix@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 4, 2015, at 2:16 PM, Greg Titus <<a href="mailto:greg@omnigroup.com" class="">greg@omnigroup.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Streza’s source code is an example of Duff’s Device, which is a big place where switch fallthrough is arguably the cleanest way to do things and the reason why I’d personally prefer to keep it as part of the language.</div></div></blockquote></div><br class=""><div class="">Yes. You beat me to it but I agree. I think having fallthrough could be an important performance optimization as refactoring would either result in the overhead of a function call or replicated code. I would also prefer to keep it in the toolbox.</div><div class=""><br class=""></div></div></div></blockquote><br class=""></div><div>I should have mentioned that 99% of the time the overhead of a function call doesn’t matter, but when it does… it is great to have.</div><div><br class=""></div><div>Ray Fix</div><div><br class=""></div><br class=""></body></html>