Skip to content

Allow parsing leap seconds #90

@ariebovenberg

Description

@ariebovenberg

Many standards and libraries allow for times like 23:59:60 to represent leap seconds, whenever should too. (Note that this is not the same as taking into account historical leap seconds, which almost no libraries or standards do)

Two approaches I can think of for this:

  1. Allow 60 seconds when ingesting or parsing data, but constrain it to 59 in the actual class (this is what JS temporal does)
  2. Representing leap seconds by allowing up to 2 seconds of micro/nanoseconds (this is what Chrono does)

Metadata

Metadata

Assignees

Labels

Long termLow priority for nowenhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions