<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jun 10, 2016 at 2:38 PM, Brandon Knope via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for the laugh!<br>
<br>
The last week or so is actually stressing me out about the direction where swift is going…<br>
<br>
I hope it is just a fleeting feeling but that remains to be seen. I am beginning to think my interests and taste are no longer aligning with the communities or core teams.<br>
<br>
Brandon<br></blockquote><div><br></div><div>I think, given the usage statistics, we'll find that these amount to small nips and tucks. I can't speak to whether things will be to your taste, but please rest assured that these proposals do not arise out of anyone's taste or distaste (outside that of the core team). If taste were the basis for proposals, I'd be proposing rather larger changes to the syntax, but I appreciate that my personal taste is of no import.</div><div><br></div><div>But as to interests, please do speak loudly and without reserve if any proposed changes are putting a stop to real-world (or even anticipated) uses you have. That's precisely what this process is about.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
> On Jun 10, 2016, at 3:25 PM, L. Mihalkovic via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
> Goodness... where is this language going.....<br>
><br>
>> On Jun 10, 2016, at 9:08 PM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>><br>
>><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>
>> <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>
>><br>
>> -- E<br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> swift-evolution mailing list<br>
>> <a href="mailto:swift-evolution@swift.org">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>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org">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">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>
</div></div></blockquote></div><br></div></div>