Skip to content
New issue

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

Uncaught exception: "missing type information" #268

Open
ryanakca opened this issue Jun 2, 2023 · 1 comment
Open

Uncaught exception: "missing type information" #268

ryanakca opened this issue Jun 2, 2023 · 1 comment
Labels
A | core affecting the typechecker B | bug unexpected or incorrect behaviour

Comments

@ryanakca
Copy link
Contributor

ryanakca commented Jun 2, 2023

Beluga crashes with an uncaught exception,

-*- mode: compilation; default-directory: "/tmp/" -*-
Compilation started at Fri Jun  2 15:04:39

beluga /tmp/mwe.bel
## Type Reconstruction begin: /tmp/mwe.bel ##
Uncaught exception.
Please report this as a bug.
Failure("missing type information")
Compilation exited abnormally with code 1 at Fri Jun  2 15:04:39

on the following minimal working example:

LF cn : type =;

LF single : type =
  | one : cn → single;

schema cns = block (c : cn);

rec crash : {g1 : cns} {g2 : cns} [ g1, a : cn ⊢ single ] → [ g1, g2, a : cn ⊢ single ] =
mlam g1 ⇒ mlam g2 ⇒ fn t1 => case t1 of
  | [ a : cn ⊢ one a ] ⇒ [ a : cn ⊢ one a ];
@MartyO256
Copy link
Member

The exception is raised during abstraction because g2 is missing an LF type annotation in [g1, g2, a : cn |- single].
More importantly, Beluga does not support contexts having two context variables.

@MartyO256 MartyO256 added B | bug unexpected or incorrect behaviour A | core affecting the typechecker labels Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A | core affecting the typechecker B | bug unexpected or incorrect behaviour
Projects
None yet
Development

No branches or pull requests

2 participants