<div dir="ltr">If you change your proposal to focus on ".values" instead of ".values.count" (which you'd get for free, as you note) I would strongly support it. I don't need ".count" on its own, but ".values" ... well, I have a whole load of enums in my current projects with a ".values" I had to hardcode myself. I would love to get that for free.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 21, 2015 at 12:46 AM, Brent Royal-Gordon 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"><span class="">> I’ve put a proposal up on GitHub to add a cases ‘count’ functionality to Enums for the Swift language<br>
> <a href="https://gist.github.com/andyyhope/2fc5b6bee8ee1346f688" rel="noreferrer" target="_blank">https://gist.github.com/andyyhope/2fc5b6bee8ee1346f688</a><br>
<br>
</span>I think we'd be much better off having a list of all cases. That would make this feature useful for enums which don't have a raw type, or don't use Int as their raw type, or don't use sequential raw values for their cases.<br>
<br>
That approach has been discussed before, but not formally proposed.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Brent Royal-Gordon<br>
Architechies<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>
</font></span></blockquote></div><br></div>