mirror of
https://github.com/unisonweb/unison.git
synced 2024-09-17 13:27:30 +03:00
2.3 KiB
2.3 KiB
structural ability X t where
x : t -> a -> a
structural ability Abort where
abort : a
I found and typechecked these definitions in scratch.u. If you
do an `add` or `update`, here's how your codebase would
change:
⍟ These new definitions are ok to `add`:
structural ability Abort
structural ability X t
.> add
⍟ I've added these definitions:
structural ability Abort
structural ability X t
This code should not type check. The match on X.x ought to introduce a
skolem variable a
such that c : a
and the continuation has type
a ->{X} b
. Thus, handle c with h : Optional a
, which is not the
correct result type.
h0 : Request {X t} b -> Optional b
h0 req = match req with
{ X.x _ c -> _ } -> handle c with h0
{ d } -> Some d
I found a value of type: Optional a1
where I expected to find: Optional a
1 | h0 : Request {X t} b -> Optional b
This code should not check because t
does not match b
.
h1 : Request {X t} b -> Optional b
h1 req = match req with
{ X.x t _ -> _ } -> handle t with h1
{ d } -> Some d
Each case of a match / with expression need to have the same
type.
Here, one is: Optional t
and another is: Optional b
3 | { X.x t _ -> _ } -> handle t with h1
4 | { d } -> Some d
from right here:
1 | h1 : Request {X t} b -> Optional b
This code should not check for reasons similar to the first example, but with the continuation rather than a parameter.
h2 : Request {Abort} r -> r
h2 req = match req with
{ Abort.abort -> k } -> handle k 5 with h2
{ r } -> r
The 1st argument to `k`
has type: Nat
but I expected: a
3 | { Abort.abort -> k } -> handle k 5 with h2
This should work fine.
h3 : Request {X b, Abort} b -> Optional b
h3 = cases
{ r } -> Some r
{ Abort.abort -> _ } -> None
{ X.x b _ -> _ } -> Some b
I found and typechecked these definitions in scratch.u. If you
do an `add` or `update`, here's how your codebase would
change:
⍟ These new definitions are ok to `add`:
h3 : Request {X b, Abort} b -> Optional b