<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="">I understand this. I am looking forward to see what Ted proposes.<div class=""><br class=""></div><div class="">-Patrick</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 19, 2016, at 2:31 PM, Ross O'Brien <<a href="mailto:narrativium+swift@gmail.com" class="">narrativium+swift@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">But the discussion is no longer about 'do we really need to take this feature out?'. The feature is already out. It's deprecated in Swift 2.2. The discussion is 'is there a compelling reason to put it back in again?'.<div class=""><br class=""></div><div class="">We still have for-in loops. We still have repeat while. We still have forEach. Iteration isn't going anywhere; it just doesn't have this peculiar semi-colon structure any more. It's a confusing structure for beginning programmers to learn in the first place, and Swift doesn't use semi-colons so much.</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sat, Mar 19, 2016 at 6:06 PM, Patrick Gili via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</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=""><br class=""><div class=""><span class=""><blockquote type="cite" class=""><div class="">On Mar 18, 2016, at 7:19 PM, Ted F.A. van Gaalen <<a href="mailto:tedvgiosdev@gmail.com" target="_blank" class="">tedvgiosdev@gmail.com</a>> wrote:</div><br class=""><div class=""><div style="word-wrap:break-word" class=""><div class="">On Chris’s advice, I’ve spawned this into a new discussion topic, for which the base could be</div><div class="">part of what I wrote in relation to SE-0007. </div><div class=""><br class=""></div><div class=""><br class=""></div>Hello Patrick<div class="">as I wrote: <br class=""><div class=""><div class=""><blockquote type="cite" class=""><div style="word-wrap:break-word" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap:break-word" class=""><div style="margin:0px;line-height:normal;color:rgb(4,51,255)" class=""><span style="font-size:12px" class=""></span></div></div></div></blockquote></div></div></div></blockquote><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class=""><div style="word-wrap:break-word" class=""><div style="margin:0px;line-height:normal;color:rgb(4,51,255)" class=""><span style="font-size:12px" class="">As a result of removing the classical for loop it is to be expected that lot of people might consider thinking twice about switching to Swift, If they have to live without (or cumbersome work around) language elements that have proven to be very useful for at least a few decades...</span></div></div></div></div></div></div></div></div></div></div></div></blockquote><div class=""><br class=""></div></span><div class="">There are two groups of people to consider:</div><div class=""><br class=""></div><div class="">1) OS X and iOS developers; this group is stuck with whatever the language brings them, for good or bad. If this group of people doesn't like a decision made by the community, they can grumble about it for awhile, suck in a deep breath, and move on.</div><div class=""><br class=""></div><div class="">2) Others; this group may be considering using Swift to develop software on other platforms and in other environments. If this group of people doesn't like a decision made by the community, they may think twice and it could significantly impact the uptake by this group of developers. I think it is wise that the community lubricate the transition to Swift as much as possible for this group of developers. I ask if leaving this kind of syntax in the language is so bad? Does it fall in the same category as removing function currying? My gut tells me not, but I could be wrong.</div><span class=""><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class=""><br class=""></div><div class="">I also find it of the most importance to keep Swift accessible for all kinds of programmers</div><div class="">from starters to academic. </div><div class=""><br class=""></div><div class="">Graig Federighi said </div><div class=""><i style="color:rgb(108,108,108);font-family:'Museo Slab',serif;font-size:26px;text-align:center;border:0px;vertical-align:baseline;margin:0px;padding:0px" class="">We think it should be everywhere and used by everyone.</i></div><div class=""><br class=""></div><div class=""><i style="color:rgb(108,108,108);font-family:'Museo Slab',serif;font-size:26px;text-align:center;border:0px;vertical-align:baseline;margin:0px;padding:0px" class=""><br class=""></i></div><div class="">I subscribe to that.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">-TedvG</div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></div></div></blockquote></span></div><br class=""></div><br class="">_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class=""></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></body></html>