<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 3, 2015, at 3:32 PM, Erica Sadun <<a href="mailto:erica@ericasadun.com" class="">erica@ericasadun.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Does Swift still needs C-style for loops with conditions and incrementers? <div class=""><br class=""></div><div class=""><div class=""><span id="cid:DD165597-A2B6-4AFA-8A16-3C9B7D693408@hsd1.co.comcast.net"><Screen Shot 2015-12-03 at 4.30.15 PM.png></span></div><div class=""><br class=""></div><div class="">More Swift-like construction is already available with <i class="">for-in</i>-statements and <i class="">stride</i>. </div><div class="">This would naturally starve the most common point for -- and ++ operators as well.</div></div></div></div></blockquote><br class=""></div><div>My intuition *completely* agrees that Swift no longer needs C-style for loops. We have richer, better-structured looping and functional algorithms. That said, one bit of data I’d like to see is how often C-style for loops are actually used in Swift. It’s something a quick crawl through Swift sources on GitHub could establish. If the feature feels anachronistic and is rarely used, it’s a good candidate for removal.</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br class=""></div><br class=""></body></html>