<div style="white-space:pre-wrap">The chapter on optionals. Right in the thick of things about if let binding, pattern matching, etc. It's a bit of a digression from the main flow of things. In the PDF version it's p. 87 (at least, by Acrobat's reckoning).<br></div><br><div class="gmail_quote"><div dir="ltr">On Sun, May 29, 2016 at 15:28 Brandon Knope <<a href="mailto:bknope@me.com">bknope@me.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div></div><div>What chapter is this in? I own this great book and would like to see what you are referring to!</div><div><br></div><div>Thanks,</div><div>Brandon </div></div><div dir="auto"><div><br>On May 29, 2016, at 11:32 AM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div style="white-space:pre-wrap">I totally agree with Brandon that it makes sense in the context. But I disagree with you: the behavior certainly isn't consistent. Those are two orthogonal evaluations.<br><br>Personally, I've never been tripped up by the two different meanings of where clauses and I've used both. Yet, when it was presented to me in prose form in _Advanced Swift_ (a great read, btw), it was a shocking thing to realize.<br><br>That these very experienced authors of the book felt compelled to point it out to their audience, who are ostensibly all experienced users of the language, suggests that there is something about the where clause not quite intuitive for all people. So I consider it a net positive to eliminate the inconsistency, whether or not it can be thought of as making sense.<br></div><br><div class="gmail_quote"><div dir="ltr">On Sun, May 29, 2016 at 11:15 Thorsten Seitz <<a href="mailto:tseitz42@icloud.com" target="_blank">tseitz42@icloud.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Totally agree with Brandon. I don’t think that behavior is inconsistent.</div><div style="word-wrap:break-word"><div><br></div><div>-Thorsten</div></div><div style="word-wrap:break-word"><div><br></div><div><br><div><blockquote type="cite"><div>Am 28.05.2016 um 22:18 schrieb Brandon Knope via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>>:</div><br><div><div dir="auto"><div></div><div>Doesn't this contextually make sense though?</div><div><br></div><div>for, when read:</div><div>"for each value in collection where some condition is met" do this loop</div><div><br></div><div>while, when read:</div><div>"while some condition where this constraint is met" do this loop </div><div><br></div><div>It could just be because I know the behavior and am use to it, but I think it makes sense contextually when used. </div><div><br></div><div>Brandon </div><div><br>On May 28, 2016, at 4:06 PM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div>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" target="_blank">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>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></div>_______________________________________________<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" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div></div></blockquote></div>
</div></blockquote></div></blockquote></div>