Idris2/libs/contrib/Data/Telescope/Fun.idr
Edwin Brady 04a0f5001f Correct multiplicities when checking Pi binders
We've always just used 0, which isn't correct if the function is going
to be used in a runtime pattern match. Now calculate correctly so that
we're explicit about which type level variables are used at runtime.

This might cause some programs to fail to compile, if they use functions
that calculate Pi types. The solution is to make those functions
explicitly 0 multiplicity. If that doesn't work, you may have been
accidentally trying to use compile-time only data at run time!

Fixes #1163
2021-03-09 17:23:05 +00:00

33 lines
1.2 KiB
Idris

||| N-ary dependent functions using telescopes
|||
||| Compare with `base/Data.Fun` and:
||| Guillaume Allais. 2019. Generic level polymorphic n-ary functions. TyDe 2019.
module Data.Telescope.Fun
import Data.Telescope.Telescope
import Data.Telescope.Segment
import Data.Telescope.SimpleFun
public export
0 Fun : (env : Left.Environment gamma) -> {n : Nat} -> (0 delta : Segment n gamma)
-> (cod : SimpleFun env delta Type)
-> Type
Fun env {n = 0 } [] cod = cod
Fun env {n = S n} (ty :: delta) cod = (x : ty env) -> Fun (env ** x) delta (cod x)
public export
uncurry : {0 n : Nat} -> {0 env : Left.Environment gamma} -> {0 delta : Segment n gamma}
-> {0 cod : SimpleFun env delta Type}
-> (f : Fun env delta cod) -> (ext : Environment env delta)
-> uncurry cod ext
uncurry f Empty = f
uncurry f (x .= xs) = Fun.uncurry (f x) xs
public export
curry : {n : Nat} -> {0 env : Left.Environment gamma} -> {0 delta : Segment n gamma}
-> {0 cod : SimpleFun env delta Type}
-> ((ext : Environment env delta) -> SimpleFun.uncurry cod ext)
-> Fun env delta cod
curry {n = 0 } {delta = [] } f = f Empty
curry {n = S n} {delta = ty :: delta} f = \x => Fun.curry (\xs => f (x .= xs))