[tz] C++20 time library

[Howard Hinnant]

On Sep 21, 2021, at 1:19 PM, Paul Eggert <eggert at cs.ucla.edu> wrote:
> 
> One other thing. Internet RFC 8536 discusses TZif file truncation, and says that TZif files should not be used to convert timestamps outside of the truncated range. This discussion is improved in the latest draft for RFC 8536's successor, here:
> 
> https://datatracker.ietf.org/doc/draft-murchison-rfc8536bis/
> 
> which also talks about expiration of leap second tables.
> 
> Should the C++20 time library address the issues of TZif truncation and leap second table expiration, or treat these issues as being out of scope? Either way, some text would be advisable.

The standard does not specify that the source form of the database is TZif, though this is likely on platforms which already deploy TZif.

Leap second table expiration is a possible feature for a future standard.  You are correct that it currently does not exist.

Howard

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <https://mm.icann.org/pipermail/tz/attachments/20210921/2126fbfc/signature-0001.asc>