Automatically generated. Retrieves the long-name constructor field of the calendarstd/time/calendar/calendar: V type.

Automatically generated. Retrieves the month-prefix constructor field of the calendarstd/time/calendar/calendar: V type.

Automatically generated. Retrieves the name constructor field of the calendarstd/time/calendar/calendar: V type.

Automatically generated. Retrieves the show-era constructor field of the calendarstd/time/calendar/calendar: V type.

Check if two calendars use the same date calculations. (Display of era names etc. may differ).

The (proleptic) Gregorian calendar. Just like the ISO calendar except that the year 0 does not exist, i.e. after 1 BCE (=~1) we have 1 CE (=1). The calendar short name is GC.

The standard ISO 8601 calendar using TI time (ts-tistd/time/utc/ts-ti: timescale). This is a proleptic Gregorian calendar except that it uses the year 0 for 1 BCE, -1 for 2 BCE etc.

This is the default calendar used in the library as it guarantees deterministic date calculations while still taking historical leap seconds into account.

The standard ISO 8601 calendar but using TI-SLS time (ts-ti-slsstd/time/utc/ts-ti-sls: timescale), i.e. TI with smoothed leap seconds.

This calendar is equivalent to the ISO calendar except for the last 1000 seconds of a day where a leap second occurs. On such day, the leap second time step (positive or negative) is distributed over the last 1000 seconds of the day. On the full hour, ISO and ISO-SLS are equal again.

This is a recommended calendar to use for time stamps or communication with other services since it avoids any potential trouble with leap seconds while still being quite precise.

Other good properties include:

• All days have 86400 seconds, and the time 23:59:60 never appears
• The time never differs more than one second from UTC
• Time as always equal to UTC on the full and half hour.

Create a standard ISO 8601 calendar using UTC time (ts-utc-createstd/time/utc/ts-utc-create: (leaps : leaps-table) -> timescale) given a provide leap second table (leaps-tablestd/time/utc/leaps-table: V). This is a proleptic Gregorian calendar except that it uses the year 0 for 1 BCE, -1 for 2 BCE etc.

You can create an ISO 8601 UTC calendar using the latest IERS leap second data using cal-utc-load.

Create a new ISO 8601 calendar based on UTC-SLS time, i.e. UTC with smoothed leap seconds.

Create a new calendar from by combining two other calendars. The switch-date is in terms of the second calendar (cal2) and time after (and including) the switch date is displayed in cal2 while times before it in cal1. This function is used for example for the Julian Gregorian calendar.

Return the days between two dates interpreted by calendar cal.

Create a calendar where we assume that each day has 24 hours with 60 minutes, and where minutes are 60 seconds (with possibly leap seconds). The function takes care of timezones, epoch shifts, and leap seconds, and only needs a calendar name, a function days-to-date to calculate a date given a number of days since the epochstd/time/instant/epoch: instant, a function date-to-days to calculate days since the epochstd/time/instant/epoch: instant for a given date, and an optional time scale to be used (=ts-utc).
month-prefix (="") is used when displaying numeric months and is set for the ISO week dates to "W" for example. The show-era function can be given to display the era of a date.

Create a standard ISO calendar using a particular time scale and calendar name (=ts.name).

An abstraction over solar calendars. Almost all calendars can be defined in terms of this function (and solar-ecalendarstd/time/calendar/solar-ecalendar: (name : string, long-name : string, days-before-year : (year : int) -> int, estimate-year : (days : int) -> (int, maybe<int>), days-before-month : (year : int, month : int) -> int, days-to-month : (year : int, doy : int) -> int, epoch-shift : ? int, has-year-zero : ? bool, month-prefix : ? string, show-era : ? ((date) -> string)) -> calendar). Given functions to convert days to and from a year, and day-of-the-year to and from month and month day, this constructs a full calendar.
Also needs an epoch-shift that gives the number of days from the calendar epoch to the date 2000-01-01. By default this is 730119 which corresponds to a 0001-01-01 ISO calendar epoch. The has-year-zero (=Truestd/core/types/True: bool) parameter is used when the calendar has a year zero. The month-prefix (="") is used for displaying numeric months (and is "W" for cal-iso-week for example). The show-era function can be given to display an era for a given date. Finally the ts (=ts-tistd/time/utc/ts-ti: timescale) gives the time scale for the calendar.

An abstraction over solar calendars. Almost all calendars can be defined in terms of this function (and solar-calendarstd/time/calendar/solar-calendar: (name : string, long-name : string, days-before-year : (year : int) -> int, days-to-yeardoy : (days : int) -> (int, int), days-before-month : (year : int, month : int) -> int, days-to-month : (year : int, doy : int) -> int, epoch-shift : ? int, has-year-zero : ? bool, month-prefix : ? string, show-era : ? ((date) -> string)) -> calendar). Given functions to convert days to and from a year, and day-of-the-year to and from month and month day, this constructs a full calendar. In contrast to solar-calendarstd/time/calendar/solar-calendar: (name : string, long-name : string, days-before-year : (year : int) -> int, days-to-yeardoy : (days : int) -> (int, int), days-before-month : (year : int, month : int) -> int, days-to-month : (year : int, doy : int) -> int, epoch-shift : ? int, has-year-zero : ? bool, month-prefix : ? string, show-era : ? ((date) -> string)) -> calendar this function just needs an estimation function from days to a year – for most calendars this is much more convenient. The estimation function returns a conservative (i.e. lowest) estimate for the year and a maybe<int> that is the safe-day: if the day of the year is lower or equal to that the estimate is surely correct. Otherwise the wrapper will calculate the start day for the next year until the correct year is found.
Also needs an epoch-shift that gives the number of days from the calendar epoch to the date 2000-01-01. By default this is 730119 which corresponds to a 0001-01-01 ISO calendar epoch. The has-year-zero (=Truestd/core/types/True: bool) parameter is used when the calendar has a year zero. The month-prefix (="") is used for displaying numeric months (and is "W" for cal-iso-week for example). The show-era function can be given to display an era for a given date. Finally the ts (=ts-utc) gives the time scale for the calendar.

Create a new calendar from anoter calendar cal by adding an offset to the years (year-shift). This is used for example to create the Ethiopian calendar from the Coptic calendar, by using: year-shift-earth-calendarstd/time/calendar/year-shift-earth-calendar: (name : string, long-name : string, year-shift : int, cal : calendar, month-prefix : ? string, show-era : ? ((date) -> string)) -> calendar( "EC", "Ethiopian", ~276, cal-coptic ).

Same timezone?

Automatically generated. Retrieves the name constructor field of the timezonestd/time/calendar/timezone: V type.

Is this the UTC timezone?

Create a time zone with a fixed number of hours and optional minutes (=0) difference from UTC/GMT. The time zone name and abbreviation is optional, and the default name will reflect the offset from UTC, for example "UTC+1:20", or "UTC-8". The default abbreviation is the empty string. The sign of the minutes will be matched to the hours (unless hours is 0). For example, tz-fixedstd/time/calendar/tz-fixed: (hours : int, mins : ? int, name : ? string, abbrv : ? string, hourwidth : ? int) -> timezone(-1,30) gives a time zone offset of -90 minutes, “UTC-1:30”. Returns tz-utcstd/time/calendar/tz-utc: timezone if both hours and mins are zero.

Return the local timezone on the current system.

The standard UTC time zone with a 0 delta.