-
Notifications
You must be signed in to change notification settings - Fork 88
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
Proof <term>.
broken
#498
Comments
Hi @mwuttke97, thanks for the detailed report! I tried this with Coq 8.11, 8.10, 8.9, and was able to reproduce this issue (but not systematically, namely depending on how I backtrack/progress in the script example); I looked at the *coq* buffer, and basically this bug seems to be reproducible with
@Matafou do you think we should report this upstream? I mean, given #188 which implies IIUC that (ultimately) we won't need to trigger Anyway for the time being, a workaround would be to do something like this (although it is more verbose):
|
I thought |
@cpitclaudel in the 8.11 refman at least, it doesn't seem to be tagged as deprecated: |
Ok, my bad then :) I thought it had been replaced by the new |
IINM you are thinking about this CEP: coq/ceps#42 But I agree that when the |
I think this is a bug that should be reported to coq. |
Hi, as pointed out by @Zimmi48 in coq/coq#12444 (comment), this issue had been reported several times already: this is a know bug for that So I'm going to close that PG issue as wont-fix. The proper fix being to do |
Hi,
Here's how to reproduce this issue:
I am using the curent
master
version of PG withCoq v8.11.1
The text was updated successfully, but these errors were encountered: