-
Notifications
You must be signed in to change notification settings - Fork 339
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
Wrong variable name in constraints for higher constructor #3660
Comments
I believe this is just an unfortunate printout. notice how If you give names in the type signature you get better names in the constraints: map : {A B : Set} → (g : A → B) → (d : D A) → D B
map f (c x) = c (f x)
map f (path x i) = path (f x) { }0 Failed to solve the following constraints:
path (g x) (?0 (f = g) (x = x) (i = i0)) = c (g x) : D B
path (g x) (?0 (f = g) (x = x) (i = i1)) = c (g x) : D B It would be great if we could get the user-provided names in the clause all the way to |
I had forgotten about this issue, but it was actually fixed in 1fd6b9f. Constraints printed now:
|
Actually, give me just a second to add a test case. |
That commit is included in 2.6.3 RC2, so I'll change the milestone to 2.6.3. |
@plt-amy, please cherry-pick the test case into the |
@asr Done, thanks for the reminder 🙂 |
This may be related to #3659, but this time it is in the unsolved constraints you get when pattern matching on a higher inductive type. Minimal example:
Agda reports the following:
The proper constraints should be like this instead:
The text was updated successfully, but these errors were encountered: