> On Jun 23, 2016, at 7:14 PM, Erica Sadun via swift-evolution
> <[email protected]> wrote:
>
>
>> On Jun 23, 2016, at 7:34 PM, William Shipley via swift-evolution
>> <[email protected] <mailto:[email protected]>> wrote:
>>
>> I’m against removing “where" from “for/in”. I use it in my code and I think
>> it aids readability quite a bit. In the example:
>>
>> for x in theArray where x % 2 == 1 { print (x) }
> I have used odd-even examples a lot when presenting this concept, and
> inevitably the response
> is "Whoa, that's cool". What I'm missing are more challenging real-world
> use-cases to justify
> the construct, and an exploration of why the challenging cases would not need
> debugger
> support at that point.
>
> My concern (and I am happy to be corrected) is that any code that becomes
> slightly more
> complex loses the beauty and readability and hinders debugging at the same
> time.
>
> — E
Here are two that are shipping right now.
for (key, tile) in self._cache where tile.tintColor != self.tintColor { }
for innerArray in actualValue where innerArray.contains(expectedElement) { }
Russ_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
