Can associated values and raw values coexist in Swift enumeration?

Question

There are examples on Swift book demonstrating associated values and raw values separately, is there a way to define enums with the two features together?

I have tri

Answer 1

I solved it like this:

enum Barcode {

   case UPCA(Int, Int, Int)// = "Order 1"
   case QRCode(String)// = "Order 2"

   static func customRawValue(rawValue: String) -> Barcode? {

       switch rawValue {

       case "Order 1": return Barcode.UPCA(0, 0, 0)
       case "Order 2": return Barcode.QRCode("")
       default: return nil
       }
    }

    var customRawValue : String {

       switch self {
       case .UPCA: return "Order 1"
       case .QRCode: return "Order 2"
       }
    }
}

if let barcode = Barcode.customRawValue("Order 1") {

   print("Barcode found with custom rawValue: \(barcode)")

   print("Custom rawValue: \(barcode.customRawValue)")
}

It's somewhat hacky, but this solution worked great for my purpose!

Answer 2

As of Swift 3 you can have both in one enum.

---

Old answer:

The error messages seem pretty clear: You have to pick one or the other.

I don't know how it works behind the scenes, so this is a guess, but it seems likely that the case arguments are stored as a tuple value where the "Raw Type" value would otherwise be stored

Answer 3

As @Jiaaro already pointed out, you cannot do that (including in Beta5).

However, it would make perfectly sense: an enum with attributed values could be implemented as a "discriminated union" or "variant" (see also wiki "tagged union"), where the "raw value" would take the role of the "tag".

That enum would then only take the space of the largest size of any attributed type plus the size of the tag (plus padding for alignment).

Answer 4

Yes this is possible. An enum may contain both associated values and raw values. (Swift 5 & 4)

Shorthand notation

The issue with your code is that you are using the shorthand notation for RawRepresentable and defining associated types.

Let's look at how to define these separately:

1) RawRepresentable (shorthand notation):

enum Barcode: String {
    case UPCA   = "order 1"
    case QRCode = "order 2"
}

2) Associated types:

enum Barcode {
    case UPCA(Int, Int, Int)
    case QRCode(String)
}

Each of these is great, but what if you need both as your code snippet shows.

Solution

Define the enum with associated values and then implement conformance to RawRepresentable separately in an extension (i.e. not using shorthand notation).

Example:

enum Barcode {
    case UPCA(Int, Int, Int)
    case QRCode(String)
}

extension Barcode: RawRepresentable {

    public typealias RawValue = String

    /// Failable Initalizer
    public init?(rawValue: RawValue) {
        switch rawValue {
        case "Order 1":  self = .UPCA(1,1,1) 
        case "Order 2":  self = .QRCode("foo")
        default:
            return nil
        } 
    }

    /// Backing raw value
    public var rawValue: RawValue {
        switch self {
        case .UPCA:     return "Order 1"
        case .QRCode:   return "Order 2"
        }
    }

}

Minor Detail

In this solution, defaults for the associated values, e.g. .UPCA(1,1,1) must be supplied when constructing the enum from the rawValue argument. You can get fancy and use the associated types as part of the backing raw value — which is more powerful, but adds some complexity.

References

For more info on the topic see Ole Begemann's excellent write up.

Answer 5

The answers here are great, but don't provide an alternative, so here is one:

I'm trying to write a convenient wrapper for Parse.com's rest API, and honestly this restriction imposed by swift made me write a bit more code, but the end result is more readable:

class Parse {

    enum Endpoint {
        case signUp(ParseHTTPBody)
        case login(ParseHTTPBody)
    }

}

extension Parse.Endpoint {

    var httpMethod: String {
        switch self {
        case .signUp, .login:
            return "POST"
        }
    }

    var path: String {
        switch self {
        case .signUp:
            return "/1/users"
        case .login:
            return "/1/login"
        }
    }
}

Notice, now I httpMethod and path instead of rawValue, which is more readable in my case:

func setParseEndpoint(endpoint: Parse.Endpoint) -> Self {

    URL = NSURL(string: baseURL + endpoint.path)
    HTTPMethod = endpoint.httpMethod

    return self
}