-
Notifications
You must be signed in to change notification settings - Fork 345
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
Internal error at CheckInternal.hs:335:10 when intentionally misusing --irrelevant-projections
#5809
Comments
This "worked" up to Agda 2.6.0 in the sense that you got a proper error:
I'll run a bisect.
|
Bisection blames commit 73ac151 (ping @jespercockx).
This is confirming my hunch/analysis that the problem is that Agda is trying to infer the type of the beta-redex agda/src/full/Agda/TypeChecking/Conversion.hs Lines 407 to 409 in 6b13364
|
@jespercockx: Isn't "Don't reduce irrelevant projections" an impossibility in our design of Agda's internal syntax?
Though, I can relate to the wish to get rid of the One way to solve this dilemma is to consider irrelevant projections as neither projections nor projection-like. So they would be |
Since irrelevant projections are not reduced since Agda 2.6.1, they can lead to non-inferable terms if they drop their parameters. A simple solution (implemented here) is to retain parameters for all irrelevant projection, treating them as ordinary functions on the rhs.
Since irrelevant projections are not reduced since Agda 2.6.1, they can lead to non-inferable terms if they drop their parameters. A simple solution (implemented here) is to retain parameters for all irrelevant projection, treating them as ordinary functions on the rhs.
Since irrelevant projections are not reduced since Agda 2.6.1, they can lead to non-inferable terms if they drop their parameters. A simple solution (implemented here) is to retain parameters for all irrelevant projection, treating them as ordinary functions on the rhs.
Since irrelevant projections are not reduced since Agda 2.6.1, they can lead to non-inferable terms if they drop their parameters. A simple solution (implemented here) is to retain parameters for all irrelevant projection, treating them as ordinary functions on the rhs.
Since irrelevant projections are not reduced since Agda 2.6.1, they can lead to non-inferable terms if they drop their parameters. A simple solution (implemented here) is to retain parameters for all irrelevant projection, treating them as ordinary functions on the rhs. Conflicts: test/Fail/Issue543.err
Since irrelevant projections are not reduced since Agda 2.6.1, they can lead to non-inferable terms if they drop their parameters. A simple solution (implemented here) is to retain parameters for all irrelevant projection, treating them as ordinary functions on the rhs. Conflicts: test/Fail/Issue543.err
Error using Agda built from commit 6b13364:
Error using Agda 2.6.2.1 (the same error):
Example:
I was intentionally using irrelevance incorrectly while trying to find an example of the sort of thing
--irrelevant-projections
can't prove. But I was hoping for a type error, not an internal error!The text was updated successfully, but these errors were encountered: