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.

Sign up for GitHub

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

Jump to bottom

Provide different interpretations of Instants #16

Open
propensive opened this issue Sep 21, 2023 · 1 comment
Open

Provide different interpretations of Instants #16

propensive opened this issue Sep 21, 2023 · 1 comment
Assignees
@propensive
Labels
enhancement An improvement to existing functionality minor Has only a small impact for the majority of users question Looking for an answer

Comments

@propensive
Copy link
Owner

propensive commented Sep 21, 2023 •
edited

Leap seconds cause all kinds of problems.

UNIX time increases by 86400 seconds every day, even on days when there is a leap second. On these days, the same numerical time can ambiguously represent distinct times (one second apart). This can affect calculations involving durations which span leap seconds.

Conversely, TAI does account for leap seconds.

I think that internally representing an Instant as TAI or UNIX time are both viable, and new instances of Instants in either representation could be constructed from UNIX timestamps or TAI timestamps, potentially raising ambiguity issues.
@propensive propensive self-assigned this Sep 21, 2023
@propensive
Copy link
Owner Author

TaiInstant has been provided in addition to Instant.

@propensive propensive added enhancement An improvement to existing functionality question Looking for an answer minor Has only a small impact for the majority of users labels Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@propensive propensive

Labels
enhancement An improvement to existing functionality minor Has only a small impact for the majority of users question Looking for an answer
Projects
Soundness
Status: Started
Milestone
No milestone
Development

No branches or pull requests
1 participant
@propensive