Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Better control over ltac backtraces #7769
Description of the problem
When using a tactic the wrong way in the Iris proof mode, we are frequently presented with error messages like this:
These traces might be useful when developing tactics, but they are certainly not useful for our users. I wouldn't even mind the short list of nested tactics very much, but literally printing the source of locally bound Ltac functions is excessive. I think per default it should not print those bound functions, so the error would become
There's still some stuff in there that users won't understand, but a least the actual error is not burried below two screen heights of dumped tactic source code.
If you are not willing to make this the default, I would appreciate at least having it available as an option.
(I somehow expected this to already be reported but couldn't find an existing report, so here you go.)
I would be strongly in favor of having an option to disable backtraces. Probably a global like
Arguably, by default it should be disabled, and one should only enable it manually when debugging tactics, but I care more about having such an option at all, than the default.