If this is a deliberate change in Kotlin (expect e...

# kotlinx-datetime

[Marc Knaup]

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

[ilya.gorbunov]

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

[Marc Knaup]

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.

[Marc Knaup]

Just now I ran into the issue that I’ve accidentally serialized Duration to database and for GraphQL with toString() instead of toIsoString() 😅
Good that I’ve got unit tests 😑

[ilya.gorbunov]

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

[Marc Knaup]

wtf happened 😂 thanks