I'm just gotta quote from Advanced Swift:<br><br>Note that the where clause [in a for loop] does not work like the where clause in a while
loop. In a while loop, iteration stops once the value is false, whereas in a for
<br>loop, it functions like filter.
<br><br><div class="gmail_quote"><div dir="ltr">On Sat, May 28, 2016 at 16:00 Haravikk <<a href="mailto:swift-evolution@haravikk.me">swift-evolution@haravikk.me</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On 28 May 2016, at 20:21, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>> wrote:<br>
><br>
> There's already an inconsistency in where clause behavior for `if` and `while` versus `for` loops. It's nice IMO that the former uses are eliminated in this proposal.<br>
<br>
Can you give an example? That sounds like something that should be addressed separately rather than just dropping it.<br>
Like I say I really like using it for basic bind + condition cases, so I’m very much opposed to just tossing where clauses.</blockquote></div>