what is the most kotlin idiomatic way to the following, so the code stays clean

# announcements

[Luis Munoz]

what is the most kotlin idiomatic way to the following, so the code stays clean

Untitled

[LeoColman]

What's wrong with this approach?

[Pablichjenkov]

if you don't have more code after the when block you can do:

fun process(someEnum: Enum) = when(someEnum) { ... }

[LeoColman]

And in some cases I would advocate for going fun Enum.process()

[Mike]

Using when as an expression will also ensure it is checked for completion. A hidden gotcha with the Kotlin when.

Depending on what 'callMethodx` does, it may make sense to convert this to sealed classes and polymorphism.

[LeoColman]

Sealed class + polymorphism seems correct, but in this case I believe it might be overly-compless

[Luis Munoz]

It is just that I read in some book that using switch statements is bad and it is better to use polymorphism, but don't know how to do that with enum

[LeoColman]

Probably some KISS will be better here

[Luis Munoz]

getFunction(someEnum).callMethod()

[LeoColman]

Instead of using an Enum you could use a Sealed Class

[Luis Munoz]

@LeoColman how would you do polymorphism with enum?

[LeoColman]

You could either add the method to the enum class or use a sealed class

[LeoColman]

An enum can h ave a method, and each constant must implement it

[Luis Munoz]

k thanks

[Pablichjenkov]

For very simple stuff Enum, for everything else Sealed Classes.
I would avoid Enum polymorphism, even though you can Override a method per constant, constant Instances will be Unique, pretty much Singletons. If you put State in it be careful of sharing it.