☰
time
time
time -- unit feature to group time related features
Value Constructors
Represents a coordinated universal date and time (UTC) in the gregorian calendar.
time.durations -- unit type defining features related to duration but not requiring
an instance
an instance
time.nano -- effect providing nano time
time.nano is a timer that provides high precision but possibly low
accuracy. Such a timer is typically useful for timing the duration
of events, such as measuring the time it takes to perform some
calculation.
time.nano may have a signficant drift compared to actual time, it might
not be the right source of time to, e.g., feed an alarm clock that should
wake you up at 6h30 every morning.
time.nano is a timer that provides high precision but possibly low
accuracy. Such a timer is typically useful for timing the duration
of events, such as measuring the time it takes to perform some
calculation.
time.nano may have a signficant drift compared to actual time, it might
not be the right source of time to, e.g., feed an alarm clock that should
wake you up at 6h30 every morning.
effect for getting the current date_time
Functions
create a String from this instance. Unless redefined, `a.as_string` will
create `"instance[T]"` where `T` is the dynamic type of `a`
create `"instance[T]"` where `T` is the dynamic type of `a`
Get the dynamic type of this instance. For value instances `x`, this is
equal to `type_of x`, but for `x` with a `ref` type `x.dynamic_type` gives
the actual runtime type, while `type_of x` results in the static
compile-time type.
There is no dynamic type of a type instance since this would result in an
endless hierarchy of types. So for Type values, dynamic_type is redefined
to just return Type.type.
equal to `type_of x`, but for `x` with a `ref` type `x.dynamic_type` gives
the actual runtime type, while `type_of x` results in the static
compile-time type.
There is no dynamic type of a type instance since this would result in an
endless hierarchy of types. So for Type values, dynamic_type is redefined
to just return Type.type.
short-hand for accessing time.nano effect in current environment
get the current date_time.
Uses currently installed time.now effect
or installs the default_now handler
Uses currently installed time.now effect
or installs the default_now handler
convenience prefix operator to create a string from a value.
This permits usage of `$` as a prefix operator in a similar way both
inside and outside of constant strings: $x and "$x" will produce the
same string.
This permits usage of `$` as a prefix operator in a similar way both
inside and outside of constant strings: $x and "$x" will produce the
same string.
stopwatch measures the execution duration of f
Reference Types
abstract handler that can deliver a nano time
Value Types
Represents a coordinated universal date and time (UTC) in the gregorian calendar.
time.duration -- value representing a duration, i.e., a time span
This is intendend for high precision time specification and measurement, it
uses a time resolution of 1ns.
The maximum value is about 580 years, so this is not intended for use in
calendars that may require time spans exceeding several centuries or millenia,
nor astrological time spans.
This is intendend for high precision time specification and measurement, it
uses a time resolution of 1ns.
The maximum value is about 580 years, so this is not intended for use in
calendars that may require time spans exceeding several centuries or millenia,
nor astrological time spans.
time.durations -- unit type defining features related to duration but not requiring
an instance
an instance
time.nano -- effect providing nano time
time.nano is a timer that provides high precision but possibly low
accuracy. Such a timer is typically useful for timing the duration
of events, such as measuring the time it takes to perform some
calculation.
time.nano may have a signficant drift compared to actual time, it might
not be the right source of time to, e.g., feed an alarm clock that should
wake you up at 6h30 every morning.
time.nano is a timer that provides high precision but possibly low
accuracy. Such a timer is typically useful for timing the duration
of events, such as measuring the time it takes to perform some
calculation.
time.nano may have a signficant drift compared to actual time, it might
not be the right source of time to, e.g., feed an alarm clock that should
wake you up at 6h30 every morning.
Type Features
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
result has the form "Type of '<name>'", but this might change in the future
There is no dynamic type of a type instance since this would result in an
endless hierarchy of types, so dynamic_type is redefined to just return
Type.type here.
endless hierarchy of types, so dynamic_type is redefined to just return
Type.type here.
Is this type assignable to a type parameter with constraint `T`?
The result of this is a compile-time constant that can be used to specialize
code for a particular type.
is_of_integer_type(n T : numeric) => T : integer
say (is_of_integer_type 1234) # true
say (is_of_integer_type 3.14) # false
it is most useful in conjunction preconditions or `if` statements as in
pair(a,b T) is
=>
or
val(n T) is
The result of this is a compile-time constant that can be used to specialize
code for a particular type.
is_of_integer_type(n T : numeric) => T : integer
say (is_of_integer_type 1234) # true
say (is_of_integer_type 3.14) # false
it is most useful in conjunction preconditions or `if` statements as in
pair(a,b T) is
=>
or
val(n T) is
name of this type, including type parameters, e.g. 'option (list i32)'.
Get a type as a value.
This is a feature with the effect equivalent to Fuzion's `expr.type` call tail.
It is recommended to use `expr.type` and not `expr.type_value`.
`type_value` is here to show how this can be implemented and to illustrate the
difference to `dynamic_type`.
This is a feature with the effect equivalent to Fuzion's `expr.type` call tail.
It is recommended to use `expr.type` and not `expr.type_value`.
`type_value` is here to show how this can be implemented and to illustrate the
difference to `dynamic_type`.