2020-05-19 20:25:18 +03:00
|
|
|
1/1: Building arity (arity.idr)
|
2021-09-15 13:57:50 +03:00
|
|
|
Error: While processing right hand side of foo. When unifying:
|
|
|
|
|
Nat -> MyN
|
|
|
|
|
and:
|
|
|
|
|
MyN
|
Remove linearity subtyping
It's disappointing to have to do this, but I think necessary because
various issue reports have shown it to be unsound (at least as far as
inference goes) and, at the very least, confusing. This patch brings us
back to the basic rules of QTT.
On the one hand, this makes the 1 multiplicity less useful, because it
means we can't flag arguments as being used exactly once which would be
useful for optimisation purposes as well as precision in the type. On
the other hand, it removes some complexity (and a hack) from
unification, and has the advantage of being correct! Also, I still
consider the 1 multiplicity an experiment.
We can still do interesting things like protocol state tracking, which
is my primary motivation at least.
Ideally, if the 1 multiplicity is going to be more generall useful,
we'll need some kind of way of doing multiplicity polymorphism in the
future. I don't think subtyping is the way (I've pretty much always come
to regret adding some form of subtyping).
Fixes #73 (and maybe some others).
2020-12-27 22:58:35 +03:00
|
|
|
Mismatch between: Nat -> MyN and MyN.
|
2020-07-28 15:11:42 +03:00
|
|
|
|
2021-06-05 14:53:22 +03:00
|
|
|
arity:4:16--4:21
|
2021-02-11 20:24:26 +03:00
|
|
|
1 | data MyN = MkN Nat Nat
|
|
|
|
|
2 |
|
|
|
|
|
3 | foo : Nat -> Nat -> Nat
|
2020-07-22 22:16:43 +03:00
|
|
|
4 | foo x y = case MkN x of
|
2021-02-11 20:24:26 +03:00
|
|
|
^^^^^
|
2020-07-28 15:11:42 +03:00
|
|
|
|
