mirror of
https://github.com/unisonweb/unison.git
synced 2024-09-11 02:25:39 +03:00
0031542faf
This is for consistency with the `cmark` style. Now the blocks we still pretty-print ourselves will match the bulk of them that `cmark` produces.
41 lines
1002 B
Markdown
41 lines
1002 B
Markdown
This is just a simple transcript to regression check an ability
|
|
inference/checking issue.
|
|
|
|
``` unison
|
|
structural ability R t where
|
|
die : () -> x
|
|
near.impl : Nat -> Either () [Nat]
|
|
|
|
R.near n = match near.impl n with
|
|
Left e -> die ()
|
|
Right a -> a
|
|
|
|
R.near1 region loc = match R.near 42 with
|
|
[loc] -> loc
|
|
ls -> R.die ()
|
|
```
|
|
|
|
``` ucm
|
|
|
|
Loading changes detected in scratch.u.
|
|
|
|
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 R t
|
|
R.near : Nat ->{R t} [Nat]
|
|
R.near1 : region -> loc ->{R t} Nat
|
|
|
|
```
|
|
The issue was that abilities with parameters like this were sometimes
|
|
causing failures like this because the variable in the parameter would
|
|
escape to a scope where it no longer made sense. Then solving would
|
|
fail because the type was invalid.
|
|
|
|
The fix was to avoid dropping certain existential variables out of
|
|
scope.
|
|
|