1

It does surprize me that this code runs:

enum Enum {
    case a, b, c, d
}

let value = Enum.a
print(value == .a) // true
print(value == .b) // false

Shouldn’t we need to conform Enum to be equatable first for it to have synthesized implementation?

1 Like
2

An enum without associated values has implicit Equatable conformance. This has always been the case for all released versions of Swift. It has been maintained even after SE-0185 for backwards compatibility.

4 Likes
3

Is there any other implicit conformance? I thought we completely eradicated them.

4

An enum without associated values also conforms implicitly to Hashable. I'm not aware that we have eradicated any implicit conformances; those are the only two.

2 Likes
5

Somehow I have the mindset of no implicit conformance. :slight_smile: