<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></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 Jun 10, 2016, at 9:24 AM, Erica Sadun <<a href="mailto:erica@ericasadun.com" class="">erica@ericasadun.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 10, 2016, at 9:22 AM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 10, 2016, at 8:02 AM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Fri, Jun 10, 2016 at 7:18 AM, Haravikk <span dir="ltr" class=""><<a href="mailto:swift-evolution@haravikk.me" target="_blank" class="">swift-evolution@haravikk.me</a>></span> wrote:<br class=""><div class="gmail_extra"><div class="gmail_quote"><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=""><div class=""><span class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">* The word "where" does not consistently imply `break` or `continue`. In current Swift, `where` implies `break` in the context of a `while` loop and `continue` in the context of a `for` loop. Some users intuitively guess the correct meaning in each context, while others guess the wrong meaning. Therefore, the only way to learn for sure what `where` means in any context is to read the rulebook. That, by definition, means that this is unintuitive.</div></div></div></div></div></blockquote><div class=""><br class=""></div></span><div class="">This is an argument for renaming the where keyword on for loops to be more clear, or to somehow integrate continue/break to be more explicit about what the developer intends for it to do.</div></div></div></blockquote><div class=""><br class=""></div><div class="">Sure: I conclude that the keyword should be *either* removed *or* reformed; both outcomes could address the issue.</div></div></div></div></div></blockquote><div class=""><br class=""></div>This is my stance as well and I reserve the right to flit between both choices until we've fully talked it through.</div><div class=""><br class=""></div><div class="">One more data point. </div><div class=""><br class=""></div><div class="">In the standard library there are just under 950 uses of "for in loops". There are 3 uses of "for in while" :</div><div class=""><br class=""></div><div class=""><div class=""><font face="Menlo" class="">private/StdlibUnittest/StdlibUnittest.swift.gyb: for j in instances.indices where i != j {</font></div><div class=""><font face="Menlo" class="">public/core/Algorithm.swift: for value in rest where value < minValue {</font></div><div class=""><font face="Menlo" class="">public/core/Algorithm.swift: for value in rest where value >= maxValue {</font></div><div class=""><br class=""></div><div class="">-- Erica</div></div></div></div></blockquote><br class=""></div><div class="">Actually a slight correction to that. I forgot to add the space after "in" on the first search. It's just over 600 and 3. Among the 600 are a few false positives but not many.</div><div class=""><br class=""></div><div class="">-- E</div></div></div></blockquote><br class=""></div><div>And to follow-up to myself once again, I went to my "Cool 3rd Party Swift Repos" folder and did the same search. Among the 15 repos in that folder, a joint search returned about 650 hits on for-in (again with some false positives) and not a single for-in-while use.</div><div><br class=""></div><div>-- E</div></body></html>