And from the WWDC Platforms SOTU: "Swift is super simple and approachable.... It's great as a first language. And in fact, we think this is so important that when we designed Swift this was an explicit design goal."<br><br>I would be absolutely against adding any more sugar to the for loop. In that sense, `where` sets a terrible example that certain features of sequences deserve contextual sugar. (And before someone points it out again, I've already argued why `for...in` holds its own weight, namely difficulty of writing a correct `while` replacement and progressive disclosure to the learner so that the concept of iterators can be learned afterwards.)<br><br>In short, I would very much be opposed to adding keywords "for fun."<br><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 14, 2016 at 11:18 AM Vladimir.S via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FWIW I don't think we need all "4", just like we don't need `unless` as a<br>
pair to current `if` or `until` as a pair for current `while` loop.<br>
<br>
I.e. we have "continue" with current `where`, and you can use boolean<br>
inversion `!`. As for "break"(while) - my opinion the for-in loop will be<br>
more powerful and adds fun for coding (from wwdc keynote - "Swift is a<br>
powerful language.. writing Swift code is *fun*..." my opinion: using<br>
guard-continue or guard-break is *not* fun ).<br>
<br>
So in your words, it is better add *one* then remove *one*.<br>
<br>
The only question I'm not sure about if we should keep 'where' and 'while'<br>
keywords for these features, or rename them. For me it's OK to have 'where'<br>
and 'while' but probably I'll support another more clear keywords.<br>
<br>
On 14.06.2016 18:01, Erica Sadun via swift-evolution wrote:<br>
><br>
>> On Jun 14, 2016, at 7:50 AM, plx via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
>> For those particular keywords, I’d prefer having them (or equivalents). I’m not sure if I’d prefer having *all* of them—`where/unless` and `while/until`—or just one from each “pair”…I could go either way.<br>
><br>
> In the proposal, my recommendations for including all 4 are:<br>
><br>
> break: while / until<br>
> continue: if (formerly `where`) / unless<br>
><br>
> As the thread has had sufficient redundancy, I'll refrain from making my case again for why I think it's better to remove the one than add the three.<br>
><br>
> -- E<br>
><br>
><br>
> _______________________________________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
><br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>