Documentation
¶
Index ¶
- func Apply[A, B any](f F1[A, B], x A) B
- func CompareOn[A, B Ord[B]](p func(A) B, x A, y A) Ordering
- func Compose[A, B, C any](f F1[B, C], g F1[A, B]) F1[A, C]
- func Const[A, B any](x A) F1[B, A]
- func Flip[A, B, C any](f F2[A, B, C]) F2[B, A, C]
- func FlipApply[A, B any](x A, f F1[A, B]) B
- func Id[A any](x A) A
- func On[A, B, C any](combine func(B, B) C, project func(A) B) func(A, A) C
- func OnHelper[A, B, C any](combine func(B, B) C, project func(A) B, x A, y A) C
- func Partial2[A, B, Z any](f F2[A, B, Z]) F1[A, F1[B, Z]]
- func Partial3[A, B, C, Z any](f F3[A, B, C, Z]) F1[A, F1[B, F1[C, Z]]]
- func Partial4[A, B, C, D, Z any](f F4[A, B, C, D, Z]) F1[A, F1[B, F1[C, F1[D, Z]]]]
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func Apply ¶
func Apply[A, B any](f F1[A, B], x A) B
Apply is from: https://hackage.haskell.org/package/base-4.16.2.0/docs/Data-Function.html#v:-36-
func CompareOn ¶
func CompareOn[A, B Ord[B]](p func(A) B, x A, y A) Ordering
CompareOn seems to be unnecessary ? TODO
func Compose ¶
func Compose[A, B, C any](f F1[B, C], g F1[A, B]) F1[A, C]
Compose is from: https://hackage.haskell.org/package/base-4.16.2.0/docs/Data-Function.html#v:.
func Const ¶
func Const[A, B any](x A) F1[B, A]
Const is from: https://hackage.haskell.org/package/base-4.16.2.0/docs/Data-Function.html#v:const
func Flip ¶
func Flip[A, B, C any](f F2[A, B, C]) F2[B, A, C]
Flip is from: https://hackage.haskell.org/package/base-4.16.2.0/docs/Data-Function.html#v:flip
func FlipApply ¶ added in v0.1.1
func FlipApply[A, B any](x A, f F1[A, B]) B
FlipApply is from: https://hackage.haskell.org/package/base-4.16.2.0/docs/Data-Function.html#v:-38-
func Id ¶
func Id[A any](x A) A
Id is from: https://hackage.haskell.org/package/base-4.16.2.0/docs/Data-Function.html#v:id
func On ¶
func On[A, B, C any](combine func(B, B) C, project func(A) B) func(A, A) C
On is from: https://hackage.haskell.org/package/base-4.16.2.0/docs/Data-Function.html#v:on
It's partially applied because the expected use case is to specify the combine/project args separately from the x/y args.
Types ¶
This section is empty.