We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On commit 6a38f01 (dev-minor).
With the following program (in a file prog.gr):
prog.gr
prog : forall a s. a [s] -> a [s] prog t = t
I get the following error message:
Checking prog.gr... Type checking failed: prog.gr: Unbound type variable: prog.gr:2:1: `_ks` is not quantified
Which ain't very friendly.
By using the debug option I was able to find that the program was interpreted as:
prog : forall {a`0 : _ka, s`1 : _ks} . a`0 [s`1] -> a`0 [s`1] prog t`2 = t`2
So it's wanting me to specify a coeffect type, which I don't really want to do (implicit forall would be nice?).
But then I thought, hang on, what about that _ka? It didn't complain about that, so I tried the following:
_ka
prog : forall {a : ka, s : Nat} . a [s] -> a [s] prog t = t
Which type-checks, which is concerning, because what is ka here??? And why is it treating "type variables" so different to grade variables?
ka
The text was updated successfully, but these errors were encountered:
No branches or pull requests
On commit 6a38f01 (dev-minor).
With the following program (in a file
prog.gr
):I get the following error message:
Which ain't very friendly.
By using the debug option I was able to find that the program was interpreted as:
So it's wanting me to specify a coeffect type, which I don't really want to do (implicit forall would be nice?).
But then I thought, hang on, what about that
_ka
? It didn't complain about that, so I tried the following:Which type-checks, which is concerning, because what is
ka
here??? And why is it treating "type variables" so different to grade variables?The text was updated successfully, but these errors were encountered: