-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kotlin.time.Instant #395
Comments
Since "Implementation on the JVM" seems to be an open question and not fully answering this: Is it the plan to copy the same implementation over as well? Wouldn't pure Kotlin implementation bring some benefits? |
A pure Kotlin implementation would be somewhat easier to support, as we would not have to introduce workarounds for the discrepancies between the JVM implementation and ours. However, introducing our own implementation to the JVM could increase the bytecode size. In general, this is just an implementation detail. What is not an implementation detail but an observable behavior is whether |
In my opinion, and from the codebases I have seen, this doesn't seem to be important as long as there is a |
This issue is for discussing the proposed transfer of
kotlinx.datetime.Instant
to the standard library askotlin.time.Instant
. The full text of the proposal is here.PR: #387
The text was updated successfully, but these errors were encountered: