<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=""><div class="">You might ease the pain by approximating C-style 'for' by a higher-order function:</div><div class=""><br class=""></div><div class="">func cStyleFor(@autoclosure init initializer: () -> (), @autoclosure test: () -> Bool, @autoclosure inc: () -> (), body: () throws -> ()) rethrows {</div><div class=""> // left as an exercise</div><div class="">}</div><div class=""><br class=""></div><div class="">var i = 0</div><div class="">cStyleFor(init: i = 0, test: i < 10, inc: ++i) {</div><div class=""> print(i)</div><div class="">}</div><div class=""><br class=""></div><div class="">-Joe</div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 4, 2015, at 2:33 PM, Colin Cornaby <<a href="mailto:colin.cornaby@mac.com" class="">colin.cornaby@mac.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div class="">I was talking with people in the office about this proposal today, in since there has been such a long discussion already I'll just reply to the top of the tree just to get our take in before the review...</div><div class=""><br class=""></div><div class="">It's understood that Swift has better, more readable ways to do for loops, but C style for loops reduce friction for getting our C or C++ developers on board with Swift. Unless there is a gain elsewhere to be made in their removal, it would be nice to keep them. As we transition to Swift we can educate developers on better ways to iterate, but it would be nice to have one less thing in the way of getting people writing Swift code.</div><div class=""><br data-mce-bogus="1" class=""></div><div class="">We work on a lot of algorithmic code which would be well suited for Swift. And again, I understand that C style for loops are redundant. But it's just one less speed bump in understanding for some of our developers or for porting pure C or C++ code without having to do as much re-validation of algorithms for accidental changes.</div><div class=""><br data-mce-bogus="1" class=""></div><div class="">But if it's actively hurting some other part of the language we could probably be talked into it.</div><div class=""><br class="">On Dec 03, 2015, at 03:32 PM, Erica Sadun <<a href="mailto:erica@ericasadun.com" class="">erica@ericasadun.com</a>> wrote:<br class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="msg-quote" style="word-wrap: break-word;" data-mce-style="word-wrap: break-word;">Does Swift still needs C-style for loops with conditions and incrementers? <div class=""><br class=""></div><div class=""><div class=""><span id="cid:10bffd09-8689-4fc6-bd44-8d6f184b8995@icloud.com"><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 class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div><img src="https://u2002410.ct.sendgrid.net/wf/open?upn=OFgvmg1J6naJevMotmPmRgzA4p1gcL5s2O89Xj3c0DQwWaI2Zkn0T7Ir0ZhZX5JxhOGd3YPVKqo7V694c-2FCbs4q0bD0JoSqDmVKJlXSPFXuXDd-2BrSCkHJtpH2xW9FNCpsnXhG1CXNS-2BYiwa2avrMmz1klqK9v719yPdWuKsBJaZWK1jLmeFzO0xSa2YmruaZcuht7m9Jfq3dmNJI2I0f-2FXBDGxRbOsbfv3np8d7UbdU-3D" alt="" width="1" height="1" border="0" style="height: 1px; width: 1px; border-width: 0; padding: 0; margin: 0;" data-mce-src="https://u2002410.ct.sendgrid.net/wf/open?upn=OFgvmg1J6naJevMotmPmRgzA4p1gcL5s2O89Xj3c0DQwWaI2Zkn0T7Ir0ZhZX5JxhOGd3YPVKqo7V694c-2FCbs4q0bD0JoSqDmVKJlXSPFXuXDd-2BrSCkHJtpH2xW9FNCpsnXhG1CXNS-2BYiwa2avrMmz1klqK9v719yPdWuKsBJaZWK1jLmeFzO0xSa2YmruaZcuht7m9Jfq3dmNJI2I0f-2FXBDGxRbOsbfv3np8d7UbdU-3D" data-mce-style="height: 1px; width: 1px; border-width: 0; padding: 0; margin: 0;" class=""></div></blockquote></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=RoDF4MveSEMYBIqIJA6ub1g8cOZ-2BVYvqV-2FqygPhjPn9dSCJq6hHxaKAHz2SgEMUEdmJq-2FsAifCMjI5P2wUJabdikvDGXS5zaIeiAW9VmUaiGFnyIyDQg2eHpiypFZpLqkwlMcSPttbgMOFlDhKsq7OZYMo2NC9kSDKFKCrEgV5UwEzHq3kVy3cvCkNDjAtbKUGaHHbyeqN4xiVXzGIrvZWzJxd5zQxuKao7pxdgeN1w-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>