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

leap seconds #377

Closed
est31 opened this issue Oct 30, 2021 · 1 comment
Closed

leap seconds #377

est31 opened this issue Oct 30, 2021 · 1 comment
Labels
C-duplicate Category: exact duplicate

Comments

@est31
Copy link

est31 commented Oct 30, 2021

I was wondering about adopting the time crate for two libraries that I maintain, rcgen and yasna. However, I've seen that there is no handling of leap seconds in time. I'm still investigating how important they are for rcgen and yasna use cases, but generally single seconds can mean a lot. Even if yasna and rcgen benefit only little from leap seconds, I think it's important to have them in a general purpose time handling library. Not everyone uses google's smeared seconds standard :).

@jhpratt
Copy link
Member

jhpratt commented Oct 30, 2021

Leap seconds inherently rely on the time zone database, which is tracked in #193. Properly handling them is extremely difficult; chrono doesn't even handle them properly.

As an aside, the issue with LetsEncrypt has nothing whatsoever to do with leap seconds.

@jhpratt jhpratt closed this as completed Oct 30, 2021
@jhpratt jhpratt added the C-duplicate Category: exact duplicate label Oct 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-duplicate Category: exact duplicate
Projects
None yet
Development

No branches or pull requests

2 participants