<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 28.07.2016, at 20:20, Karl Wagner <<a href="mailto:razielim@gmail.com" class="">razielim@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div id="edo-message" class=""><div class="">+1. There have been lots of accepted proposals which I argued against, but community-driven evolution means we have to compromise.</div></div></div></div></blockquote>This would imply, that if a decision is made, which in a later and changed context proves to be a bad one, would be irreversible? </div><div>Better turn half way than to err in continuing.</div><div>Or, one decides to go diving, but arriving at the location, notice that the water is full of sharks? Still continue? </div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div id="edo-message" class=""><div class=""><br class=""></div><div class="">In Plato's Crito, Socrates refuses to flee Athens after being sentenced to death. He entered in to an agreement with the state to participate in the process and respect its judgements, and reasons that to violate the rules of the system because he believes the outcome unjust would be a greater injustice.</div><div class=""><br class=""></div><div class="">Just mentioning it; it's always been a fascinating story to me.</div></div></div></div></blockquote>Thanks, interesting. Long ago I’ve read a bit in Plato - The Republic but was back then</div><div>to hyper active to concentrate..<br class=""><blockquote type="cite" class=""><div class=""><div class=""><div id="edo-message" class=""><div class=""><br class=""></div><div class="">Karl</div><div class=""><br class=""><div style="font-family: 'Helvetica Neue','Helvetica',Helvetica,Arial,sans-serif;font:'-apple-system-body';" class="">Sent from my new <a href="https://itunes.apple.com/app/apple-store/id922793622?pt=814382&mt=8&ct=my_new_email" class="">Email</a></div></div></div><div id="edo-original" class=""><div class=""><br class=""></div></div></div></div></blockquote>TedvG<br class=""><blockquote type="cite" class=""><div class=""><div class=""><div id="edo-original" class=""><div class=""><br class=""><blockquote type="cite" style="margin:1ex 0 0 0;border-left:1px #ccc solid;padding-left:0.5ex;" class=""><div class="">On Jul 28, 2016 at 7:33 PM, <<a href="mailto:swift-evolution@swift.org" class="">Austin Zheng via swift-evolution</a>> wrote:<br class=""><br class=""></div><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><br class=""><div class=""><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 class=""><br class=""></div><div class="">I don't understand why you keep on complaining about this.</div><div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">However,</div><div class=""><br class=""></div><div class="">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 class="">2. That process includes feedback and review from both the community and the Swift core engineers, and often multiple rounds of discussion.</div><div class="">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 class=""><br class=""></div><div class="">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 class=""><i class=""><br class=""></i></div><div class="">Best regards,</div><div class=""><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="">_______________________________________________
swift-evolution mailing list
<a dir="ltr" href="mailto:swift-evolution@swift.org" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="4" class="">swift-evolution@swift.org</a>
<a dir="ltr" href="https://lists.swift.org/mailman/listinfo/swift-evolution" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="5" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a>
</div></blockquote></div></div></div></div></blockquote></div><br class=""></body></html>