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

What's wrong with this approach?

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

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

And in some cases I would advocate for going

fun Enum.process()

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.

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

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

Probably some KISS will be better here

getFunction(someEnum).callMethod()

Instead of using an Enum you could use a Sealed Class

@LeoColman how would you do polymorphism with enum?

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

k thanks

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.