kotlinx-datetime

https://github.com/Kotlin/kotlinx-datetime

Since it seems that it actual/expect things Klock has a different approach. It needs allocation-free primitives for the rest of the korlibs stack, so maybe the approach will be to create a klock-kotlinx-datetime artifact providing interoperability while still having an allocation and dependency-free version.

Start by comparing the linked kotlinx-datetime project with the Klock approach described in the issue, then inspect the korlibs-time repository to identify the relevant time primitives and platform boundaries. The issue does not name files, tests, or acceptance criteria, so the desired artifact and allocation- and dependency-free behavior need clarification before implementation.

Written by the indexing model from the issue text.