What’s our strategy on the time API? Do we keep on...
# arrow-contributors
p
What’s our strategy on the time API? Do we keep on using arrow’s Duration for new APIs or do we use
kotlin.time
instead? I’m asking as it requires opt-in 🙂
s
We were kind of waiting for
kotlin.time
to stop being experimental, but it seems that's taking much longer than we expected 😕 What is Jetbrains stance on using
kotlin.time
? Are they suggesting to move ahead with it and just annotate it? They seem to have non
kotlin.time
available APIs in KotlinX next to their
kotlin.time
APIs.
p
I guess, the more user friendly option may be to offer both alternatives. One that takes Arrow’s Duration and another one that forces the user to use the opt in annotation
Which should make it easier to deprecate once kotlin.time is final
s
Makes perfect sense!