[swift-evolution] Working with enums by name
me at lmpessoa.com
Tue May 31 20:31:32 CDT 2016
If I got the idea right, you would need to implement yourself the protocol methods to answer for both init(rawValue: Int) and init(rawValue: String) - which is how you have to do today only with the string part - while my proposed approach you'd have to implement nothing yourself.
> On 31 May 2016, at 7:19 pm, Austin Zheng via swift-evolution <swift-evolution at swift.org> wrote:
> If we had generic protocols, you could implement RawRepresentable twice, once using Ints and one using Strings. But that's probably never going to happen.
>> On Tue, May 31, 2016 at 3:11 PM, Erica Sadun via swift-evolution <swift-evolution at swift.org> wrote:
>> > On May 31, 2016, at 4:07 PM, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> wrote:
>> >> • also wants OptionSetType-like behavior (and thus an Int raw type).
>> > Then it's not an `enum`, it's a `struct`.
>> You can get it for free as an array of enums and test with contains vs member
>> -- E, who has probably digressed more than she really should
>> swift-evolution mailing list
>> swift-evolution at swift.org
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution