☰
infix ||>
infix ||>
§(A type, B type, R type, a tuple (infix ||>.A) (infix ||>.B), f Function (infix ||>.R) (infix ||>.A) (infix ||>.B)):Any => infix ||>.R
§(A
type
, B type
, R type
, a tuple (infix ||>.A) (infix ||>.B), f Function (infix ||>.R) (infix ||>.A) (infix ||>.B)):
Any =>
infix ||>.RFunctions
create a String from this instance. Unless redefined, `a.as_string` will
create `"instance[T]"` where `T` is the dynamic type of `a`
create `"instance[T]"` where `T` is the dynamic type of `a`
Get the dynamic type of this instance. For value instances `x`, this is
equal to `type_of x`, but for `x` with a `ref` type `x.dynamic_type` gives
the actual runtime type, while `type_of x` results in the static
compile-time type.
There is no dynamic type of a type instance since this would result in an
endless hierachy 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 hierachy of types. So for Type values, dynamic_type is redefined
to just return Type.type.
This allows changing the order of function application: instead of
f(a,b i32) => a+b
l1 := [1,2,3,4]
l2 := [4,3,2,1]
l := l1.pairs l2
you can write
l1 := [1,2,3,4]
l2 := [4,3,2,1]
l := l1.pairs l2
which often correponds more naturally to the data flow through the code.