package async

Note that we expose a sexp format that is not the one exposed in Core.

Because timezone offsets change throughout the year (clocks go forward or back) some local times can occur twice or not at all. In the case that they occur twice, this function gives `Twice with both occurrences in order; if they do not occur at all, this function gives `Never with the time at which the local clock skips over the desired time of day.

Note that this is really only intended to work with DST transitions and not unusual or dramatic changes, like the calendar change in 1752 (run "cal 9 1752" in a shell to see). In particular it makes the assumption that midnight of each day is unambiguous.

Most callers should use of_date_ofday rather than this function. In the `Twice and `Never cases, of_date_ofday will return reasonable times for most uses.

Always returns the Date.t * Ofday.t that to_date_ofday would have returned, and in addition returns a variant indicating whether the time is associated with a time zone transition.

      - `Only         -> there is a one-to-one mapping between [t]'s and
                         [Date.t * Ofday.t] pairs
      - `Also_at      -> there is another [t] that maps to the same [Date.t * Ofday.t]
                         (this date/time pair happened twice because the clock fell back)
      - `Also_skipped -> there is another [Date.t * Ofday.t] pair that never happened (due
                         to a jump forward) that [of_date_ofday] would map to the same
                         [t].

For performance testing only; reset_date_cache () resets an internal cache used to speed up to_date and related functions when called repeatedly on times that fall within the same day.

It's unspecified what happens if the given date/ofday/zone correspond to more than one date/ofday pair in the other zone.

to_filename_string t ~zone converts t to string with format YYYY-MM-DD_HH-MM-SS.mmm which is suitable for using in filenames.

of_filename_string s ~zone converts s that has format YYYY-MM-DD_HH-MM-SS.mmm into time.

to_string_abs ~zone t is the same as to_string t except that it uses the given time zone.

to_string_abs_trimmed is the same as to_string_abs, but drops trailing seconds and milliseconds if they are 0.

Same as to_string_abs_trimmed, except it leaves off the timezone, so won't reliably round trip.

Same as to_string_abs, but without milliseconds

of_localized_string ~zone str read in the given string assuming that it represents a time in zone and return the appropriate Time.t

of_string_gen ~default_zone ~find_zone s attempts to parse s as a t, calling out to default_zone and find_zone as needed.

to_string_iso8601_basic return a string representation of the following form: %Y-%m-%dT%H:%M:%S.%s%Z e.g. to_string_iso8601_basic ~zone:Time.Zone.utc epoch = "1970-01-01T00:00:00.000000Z"

occurrence side time ~ofday ~zone returns a Time.t that is the occurrence of ofday (in the given zone) that is the latest occurrence (<=) time or the earliest occurrence (>=) time, according to side.

NOTE: If the given time converted to wall clock time in the given zone is equal to ofday then the t returned will be equal to the t given.

Unix epoch (1970-01-01 00:00:00 UTC)

The minimum representable time.

The maximum representable time.

The minimum time that rounds to a Time.t with microsecond precision.

The maximum time that rounds to a Time.t with microsecond precision.

An alias for min_value_for_1us_rounding.

• deprecated [since 2019-02] use [min_value_representable] or [min_value_for_1us_rounding] instead

An alias for max_value_for_1us_rounding.

• deprecated [since 2019-02] use [max_value_representable] or [max_value_for_1us_rounding] instead

The current time.

overflows silently

As add; rather than over/underflowing, clamps the result to the closed interval between min_value_representable and max_value_representable.

As sub; rather than over/underflowing, clamps the result to the closed interval between min_value_representable and max_value_representable.

overflows silently

overflows silently

overflows silently

overflows silently

overflows silently

Will raise on 32-bit platforms. Consider to_int63_ns_since_epoch instead.

next_multiple ~base ~after ~interval returns the smallest time of the form:

time = base + k * interval

where k >= 0 and time > after. It is an error if interval <= 0.

Supplying ~can_equal_after:true allows the result to satisfy time >= after.

Overflows silently.

prev_multiple ~base ~before ~interval returns the largest time of the form:

time = base + k * interval

where k >= 0 and time < before. It is an error if interval <= 0.

Supplying ~can_equal_before:true allows the result to satisfy time <= before.

• deprecated [since 2019-01] use [of_time_float_round_nearest] or [of_time_float_round_nearest_microsecond]

• deprecated [since 2019-01] use [to_time_float_round_nearest] or [to_time_float_round_nearest_microsecond]