If this is a deliberate change in Kotlin (expect enums no longer exhaustive) then please don’t use

expect enum

in

kotlinx-datetime

😕 https://github.com/Kotlin/kotlinx-datetime/issues/96

We know about the exhaustiveness problem of expect enums and sealed classes/interfaces. We might eventually solve it with https://youtrack.jetbrains.com/issue/KT-38750

That would improve the situation. There are more issues with typaliasing instead of having its own enum though, as mentioned in the GitHub issue. I’d prefer to have it fixed & improved from the library’s side. Just fixing the new exhaustiveness problem only solves one of the existing issues.

Did you mean to post in the other thread (this is about enums)? 🙂

wtf happened 😂 thanks