<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=""><div class="">Hi Austin,</div><div class=""><br class=""></div><div class=""><div>please read inline.<br class=""><blockquote type="cite" class=""><div class="">On 28.07.2016, at 23:47, Austin Zheng <<a href="mailto:austinzheng@gmail.com" class="">austinzheng@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Jul 28, 2016 at 2:37 PM, Ted F.A. van Gaalen <span dir="ltr" class=""><<a href="mailto:tedvgiosdev@gmail.com" target="_blank" class="">tedvgiosdev@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Hi Austin, thank you, please see inline<div class=""><div class="">? </div>I have explained this many times before, didn’t I? </div><div class=""><br class=""></div><div class="">Its removal causes a very crucial limitation/change in the way </div><div class="">one writes programs, So writing about this for;; subject is</div><div class="">very, very different from long discussions like those about </div><div class="">allowing a comma at the end of a list or not…</div><div class="">because removing the for;; has a very heavy impact.</div><div class=""><br class=""></div><div class="">Furthermore, IMHO the decision to remove the for;; was based</div><div class="">on very subjective loose and partly irrelevant criteria.</div><div class=""><br class=""></div></div></blockquote><div class=""><br class=""></div><div class="">I don't care how good your reasons are, the fact of the matter is that it was extensively discussed, a decision was made, and it is now a done deal.</div></div></div></div></div></blockquote>Napoleon said something similar when pushing his army towards Moscow...<br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""> Please remember that these are high-traffic lists that many people subscribe to; complaining about the C for loop is a waste of everybody's time.</div></div></div></div></div></blockquote>That’s your opinion.<br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""> At the very least, please respect the process and put together a proposal that we can all discuss,</div></div></div></div></div></blockquote><div>As written before, I will write the proposal after Swift 3.0 is released.</div><div>If you are interested in bringing it back then you could help</div><div>me with it.</div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""> instead of asking Chris or whoever to step in and make an exception because you don't like it.</div></div></div></div></div></blockquote>Yes, indeed, I am exceptionally asking to make an exception, to keep the for ;; in<div class="">for the time being.</div><div class=""><br class=""></div><div class="">As concerning your “high traffic” notion, this is written material</div><div class="">no doubt, the recipients are capable enough to put it aside for later</div><div class="">if they’d wish to do so. </div><div class=""><br class=""></div><div class=""><div class=""><div>Sorry, if you don’t like it.</div><div>Thanks.</div><div>TedvG</div></div></div><div><br class=""></div><div class=""><br class=""></div></div><br class=""></div></body></html>