> On Jan 10, 2018, at 2:23 PM, Kevin Nattinger <sw...@nattinger.net> wrote:
>
>> [...]
>>
>> I don’t agree that the Collection should be Int-indexed. Source-order is not
>> a very strong guarantee IMO, and it wouldn’t be good if people started
>> writing things like "MyEnum.allValues[3]” to reference a specific case.
>
> So how do you propose to use allValues with a table view? That's one of the
> motivating examples, and probably the most common use case. Certainly the
> most common I've seen.
I assume the mildly inconvenient
static let valuesForTableView = Array(MyEnum.allValues)
…or some such.
>
>>
>> If you know the specific case you are looking for, just write it directly.
>> If you found an interesting case while iterating allValues, remember its
>> (opaque) index and come back to it later.
>>
>> I’m not a fan of Int-indexes in general. It’s practical to allow it for
>> Array, but in general, for generic Collections, I think it implies an awful
>> lot of knowledge about the Collection’s contents.
>>
>> - Karl
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution@swift.org <mailto:swift-evolution@swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
