<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jun 10, 2016 at 2:08 PM, Erica Sadun <span dir="ltr"><<a href="mailto:erica@ericasadun.com" target="_blank">erica@ericasadun.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Jun 10, 2016, at 1:06 PM, Rob Norback via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
> Following Brent's logic that the for-in where should mimic the switch statement functionality, then this example:<br>
><br>
> for (eachKey, eachValue)<br>
> where eachValue > 5<br>
> in theKeyValuePairs {... }<br>
><br>
<br>
</span><squish><br>
<br>
I finally convinced myself of which direction I wanted to go: <a href="https://github.com/apple/swift-evolution/pull/362/files" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/pull/362/files</a><br>
<br>
Related blog post here: <a href="http://ericasadun.com/2016/06/10/swift-where-oh-where-can-my-where-clause-be/" rel="noreferrer" target="_blank">http://ericasadun.com/2016/06/10/swift-where-oh-where-can-my-where-clause-be/</a><br>
<br>
Big thanks to Brent and Wux.<br></blockquote><div><br></div><div>I'm rather taken by the idea of replacing `where` with `if` for `case` and `catch`: it's unambiguous and eliminates the implication of a subordinate semantic relationship which can't actually be enforced, while still exposing all of the expressiveness made possible by `where` in that particular scenario.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
-- E<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>