Like I said, you can write the same kind of thing very easily in Kotlin by using a sealed class - your example would translate line-for-line. It's a useful feature. But it's very confusing to call it a kind of enum rather than as a kind of class; as your other post acknowledges, it means Swift essentially has two different things that are differently implemented but both called "enum".
But they don't make sense as enums. If you have to look "under the hood" to get a reasonable model of a feature, it's a bad design.
> It's quite powerful, once you get your head around it.
> I write about that here: https://littlegreenviper.com/miscellany/swiftwater/enums-wit....
Like I said, you can write the same kind of thing very easily in Kotlin by using a sealed class - your example would translate line-for-line. It's a useful feature. But it's very confusing to call it a kind of enum rather than as a kind of class; as your other post acknowledges, it means Swift essentially has two different things that are differently implemented but both called "enum".