<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 Jul 28, 2016, at 10:19 AM, Ted F.A. van Gaalen via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class=""> -= Maybe it’s not too late =- </div><div class="">For the moment the classical for ;; could simply </div><div class="">remain activated (Yes) in 3.0. because: </div></div></div></blockquote><div><br class=""></div><div>I don't understand why you keep on complaining about this.</div><div><br class=""></div><div>For the record, I too think getting rid of the C-style for loop was a mistake, and there are a number of other proposals whose outcomes are not ones I would have personally preferred.</div><div><br class=""></div><div>However,</div><div><br class=""></div><div>1. There is a well-defined process through which all changes to the Swift language must go, laid out in the swift-evolution repository's documentation from the first day Swift became an open-source project.</div><div>2. That process includes feedback and review from both the community and the Swift core engineers, and often multiple rounds of discussion.</div><div>3. The process doesn't work if we disregard its outcomes simply because we don't like them, or if we allow interminable chains of back-and-forth proposals because people on one side of issue X simply cannot accept a particular decision.</div><div><br class=""></div><div>The technical aspects of the C-style for loop and its proposed replacements have already been discussed <i class="">ad nauseam</i> on this list and in other places, so I won't touch on them.</div><div><i class=""><br class=""></i></div><div>Best regards,</div><div><i class="">Austin </i> </div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""> </div><div class=""> - It doesn’t conflict at all with all other language elements,</div></div></div></blockquote></div><br class=""></body></html>