-
Notifications
You must be signed in to change notification settings - Fork 338
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
de Bruijn index out of scope when rewriting #6003
Comments
I got a similar error elsewhere in my code:
It seems reasonably likely that this has the same or similar cause, since it cites the same line of the Agda source. If it would be helpful to have another example, let me know and I can post the second one. (It will start out with the same long setup, but the error is triggered by something different.) (I am aware that I'm doing terrible things to subject reduction. But I would assume that even this shouldn't cause de Bruijn indices to go out of scope.) |
Would it be helpful in fixing this if I were able to make the test case smaller? (Sorry if this is a dumb question, I don't really have any idea whether the size of the triggering code affects the difficulty of tracking down a bug like this.) |
Yes, this always helps, because focusing the trigger will usually give some idea where the bug could reside (helps understanding the test case), and, trivially, there will be less clutter if debug-printing is turned on. |
…plicitPatternsT`
…plicitPatternsT`
Fantastic! Thanks for fixing this, even with such a long test case. As I expected, the fix has also fixed the other similar error. |
Agda 2.6.0 still said correctly:
|
I'm sorry that this example is so long; I wasn't able to remove any parts of it and still reproduce the error.
In Agda 2.6.3-5d2d77a this produces
The text was updated successfully, but these errors were encountered: