+1 for ".values" instead of just ".count". Really handy feature that Java has. In Java it returns a set not an array which is great for representing status. In C you would use a bit field, but an enum set is better.
Sent from my iPad > On 21 Dec 2015, at 7:57 PM, Charles Constant via swift-evolution > <[email protected]> wrote: > > 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. > >> On Mon, Dec 21, 2015 at 12:46 AM, Brent Royal-Gordon via swift-evolution >> <[email protected]> wrote: >> > I’ve put a proposal up on GitHub to add a cases ‘count’ functionality to >> > Enums for the Swift language >> > https://gist.github.com/andyyhope/2fc5b6bee8ee1346f688 >> >> 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. >> >> That approach has been discussed before, but not formally proposed. >> >> -- >> Brent Royal-Gordon >> Architechies >> >> _______________________________________________ >> swift-evolution mailing list >> [email protected] >> https://lists.swift.org/mailman/listinfo/swift-evolution > > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
