Comparing enum cases while ignoring associated values

[Dmitriy_Ignatyev]

Hello. This topic is regularly being discussed. Some of the discussions:

Pitch: Auto-synthesize cases for enums

To go along with the recently reviewed Derived Collection of Enum Cases, I'd like to propose that we also derive a Case enum for all enums. The problem One of the biggest issues I have with using enums is that comparing the case of two enums is really painful. Take for example, if I decided to make a game called Orc vs Elves vs Humans, and decided to represent them as an enum enum Race { case orc(weapon: Weapon) case elf(spell: MagicSpell) case human(karateMove: KarateMove) func atta…

DiscriminatedUnion Protocol

I've had this idea for a while but have been distracted by a great many things. My hand has been forced, a little, by Extract Payload for enum cases having associated value - #140 by gwendal.roue. I consider this a possible alternative. I admit that I've stopped following the thread consistently but I've checked in on the thread every now and then. Motivation There are times when you need to construct a decision tree about and enum well before you have an instance of that enum. Consider a sta…

As current workaround, you can use this solution:

Getting the name of a Swift enum value

I don't like to advertise, but a user of a library I'm working on had this exact issue. While I agree that the standard library could probably vend it's own way to give this information to users, I have an interim solution here: Accessing name of enum with a raw value · Issue #9 · Azoy/Echo · GitHub. (I believe everything in this solution is ABI stable on Darwin platforms.) This just looks at the enum metadata to get it's name.

But be careful and keep in mind, it is not safe and can be broken in future.