If you need instances, that sounds more like sealed classes than enums

I don’t need instances per se, but that’s how enum entries are represented in Kotlin anyhow.

I’m kinda just asking for my own benefit at this point, but I’m curious what the use case is for an interface that mandates classes themselves provide a method but not the class instances

It's pretty easy to write function like this btw, just have a parameter in the enum constructor and then in the companion object

fun fromInt(int: Int) = MyEnum.values.first { it.day == int }

@Shawn This is correct.