Skip to content
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

Add conversion of Instant to/from Unix epoch second + nanosecond #9

Merged
merged 5 commits into from
Jun 11, 2020

Conversation

dkhalanskyjb
Copy link
Collaborator

Before, Instant did use nanosecond precision internally, and it
could be accessed by adding or substracting time periods or
constructing a new Instant by parsing a string with a nanosecond
component. Now, all the internal state of an Instant is more
easily accessible.

Before, Instant did use nanosecond precision internally, and it
could be accessed by adding or substracting time periods or
constructing a new Instant by parsing a string with a nanosecond
component. Now, all the internal state of an `Instant` is more
easily accessible.
@dkhalanskyjb dkhalanskyjb requested a review from ilya-g May 6, 2020 08:32
It is customary to use the full measurement unit names in Kotlin
libraries, so having "Millis" as an exception was harming
consistency.

Also, "Unix time" was deemed similar enough to our notion of the
time epoch, and so the two names were unified.
@dkhalanskyjb dkhalanskyjb force-pushed the Instant.epochSeconds branch from fff5725 to be549e4 Compare June 5, 2020 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants