☰
wrap_around
num.wrap_around
Constructors
absolute value using `|a|` built from a `prefix |` and `postfix |` as an operator
alias of `a.abs`
Due to the low precedence of `|`, this works also on expressions like `|a-b|`, even
with spaces `| a-b |`, `|a - b|`, `| a-b|` or `|a-b |`.
Nesting, however, does not work, e.g, `| - |a| |`, this requires parentheses `|(- |a|)|`.
NYI: CLEANUP: Due to #3081, we need `postfix |` as the first operation, should be
`prefix |` firstFunctions
absolute value
this integer as an array of bytes (little endian)
convert this to a decimal number in a string. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character. Extend with leading "0" until the length is at
least len
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
Constructors
absolute value using `|a|` built from a `prefix |` and `postfix |` as an operator
alias of `a.abs`
Due to the low precedence of `|`, this works also on expressions like `|a-b|`, even
with spaces `| a-b |`, `|a - b|`, `| a-b|` or `|a-b |`.
Nesting, however, does not work, e.g, `| - |a| |`, this requires parentheses `|(- |a|)|`.
NYI: CLEANUP: Due to #3081, we need `postfix |` as the first operation, should be
`prefix |` firstFunctions
absolute value
this integer as an array of bytes (little endian)
convert this to a decimal number in a string. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character. Extend with leading "0" until the length is at
least len
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
absolute value using `|a|` built from a `prefix |` and `postfix |` as an operator
alias of `a.abs`
Due to the low precedence of `|`, this works also on expressions like `|a-b|`, even
with spaces `| a-b |`, `|a - b|`, `| a-b|` or `|a-b |`.
Nesting, however, does not work, e.g, `| - |a| |`, this requires parentheses `|(- |a|)|`.
NYI: CLEANUP: Due to #3081, we need `postfix |` as the first operation, should be
`prefix |` first
alias of `a.abs`
Due to the low precedence of `|`, this works also on expressions like `|a-b|`, even
with spaces `| a-b |`, `|a - b|`, `| a-b|` or `|a-b |`.
Nesting, however, does not work, e.g, `| - |a| |`, this requires parentheses `|(- |a|)|`.
NYI: CLEANUP: Due to #3081, we need `postfix |` as the first operation, should be
`prefix |` first
Functions
absolute value
this integer as an array of bytes (little endian)
convert this to a decimal number in a string. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character. Extend with leading "0" until the length is at
least len
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
absolute value
this integer as an array of bytes (little endian)
convert this to a decimal number in a string. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character. Extend with leading "0" until the length is at
least len
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
this integer as an array of bytes (little endian)
convert this to a decimal number in a string. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character. Extend with leading "0" until the length is at
least len
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
convert this to a decimal number in a string. If negative, add "-" as
the first character.
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character. Extend with leading "0" until the length is at
least len
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
convert this to a number using the given base. If negative, add "-" as
the first character.
the first character.
convert this to a number using the given base. If negative, add "-" as
the first character. Extend with leading "0" until the length is at
least len
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
convert this to a number using the given base. If negative, add "-" as
the first character. Extend with leading "0" until the length is at
least len
the first character. Extend with leading "0" until the length is at
least len
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
this numeric value as an u8
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create binary representation
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create binary representation with given number of digits.
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create decimal representation
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create decimal representation with given number of digits.
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
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.
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
does this numeric value fit into an u8? This is redefined by children
of numeric that support `as_u8`.
of numeric that support `as_u8`.
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
greatest common divisor of this and b
note that this assumes zero to be divisible by any positive integer.
note that this assumes zero to be divisible by any positive integer.
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create hexadecimal representation
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create hexadecimal representation with given number of digits.
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
basic operations: 'infix %' (division remainder)
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
test divisibility by other
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
bitwise operations
§multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
multiplication, with check for overflow
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
exponentiation for positive exponent
'zero ** zero' is permitted and results in 'one'.
'zero ** zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix **?]exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
(other num.this.wrap_around.this)
=>
option num.this.wrap_around.this [Redefinition of numeric.infix **?]
exponentiation with overflow checking semantics
'zero **? zero' is permitted and results in 'one'.
'zero **? zero' is permitted and results in 'one'.
§exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
exponentiation with saturating semantics
'zero **^ zero' is permitted and results in 'one'.
'zero **^ zero' is permitted and results in 'one'.
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
exponentiation with wrap-around semantics
'zero **° zero' is permitted and results in 'one'.
'zero **° zero' is permitted and results in 'one'.
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
(other num.this.wrap_around.this)
=>
option num.this.wrap_around.this [Redefinition of numeric.infix *?]
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
addition, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
(other num.this.wrap_around.this)
=>
option num.this.wrap_around.this [Redefinition of numeric.infix +?]
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
subtraction, with check for overflow
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§(other num.this.wrap_around.this) => option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
(other num.this.wrap_around.this)
=>
option num.this.wrap_around.this [Redefinition of numeric.infix -?]
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
§
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
basic operations: 'infix /' (division)
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
operation is permitted for the given values
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create a fraction
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
shift operations
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create a fraction via unicode fraction slash \u2044 '⁄ '
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
check if this type of wrap_around is bounded
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
wrap_arounds are assumed to be a bound set by default, so
this returns true unless redefined by an implementation
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create octal representation
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
create octal representation with given number of digits.
count the number of 1 bits in the binary representation of this
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
count the number of 1 bits in the binary representation of this
integer.
integer.
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would addition wrap_around.this + other cause an overflow or underflow?
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would exponentiation 'this ** other' cause an overflow?
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would multiplication wrap_around.this * other cause an overflow or underflow?
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would subtraction wrap_around.this - other cause an overflow or underflow?
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
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.
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
basic operations: 'prefix +' (identity)
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
preconditions for basic operations: true if the operation's result is
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
representable and defined for the given values
default implementations all return `true` such that children have to
redefine these only for partial operations such as those resulting in
an overflow or that are undefined like a division by zero for most
types.
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
negation, with check for overflow
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
preconditions used in 'numeric' for basic operations: true if the
operation is permitted for the given values
operation is permitted for the given values
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
overflow checking operations
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
saturating operations
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
neg, add, sub, mul with wrap-around semantics
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
bitwise NOT
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
bitwise NOT (Unicode alias)
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
sign function resulting in `-1`/`0`/`+1` depending on whether `numeric.this`
is less than, equal or larger than zero
is less than, equal or larger than zero
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
would negation -wrap_around.this cause an overflow?
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
Type Functions
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
returns the number in whose bit representation all bits are ones
string representation of this type to be used for debugging.
result has the form "Type of '<name>'", but this might change in the future
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
wrap_around is the abstract ancestor of integer numbers that have min and
max values and operations with wrap-around semantics.