-
Notifications
You must be signed in to change notification settings - Fork 18
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
surprising behavior of intros
when names are given in unexpected way.
#97
Comments
In fact, explicitly giving I guess the fix is: whenever the user chooses a variable name, checks if it coincides with the "next fresh name", and in that case increment the fresh name counter (do as if it had been generated by the system). |
I've committed a quick fix but it has a performance impact. Not sure how
measurable. Also it may break some existing proofs because the numbering is
different in some corner cases. Will need to revisit this.
…On Mon, Jan 8, 2018 at 12:19 PM, Gabriel Scherer ***@***.***> wrote:
In fact, explicitly giving intros H1 H2. works badly even if the correct
number of variables are given, because it disturbs the fresh-name
generation later in the script to reuse H1 and H2 again. This means that
given a script that uses intros., rewriting it to use intros H1 ... Hn
explicitly will in general break the rest of the proof script as it will
change the generated variable names.
I guess the fix is: whenever the user chooses a variable name, checks if
it coincides with the "next fresh name", and in that case increment the
fresh name counter (do as if it had been generated by the system).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#97 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjB6JASK-9HMLtoRKsRk9uAJgT7N5v-ks5tIfnGgaJpZM4RWOtE>
.
|
This breaks too many existing proofs. More testing is needed. |
intros <name>*
is not documented in the reference manual. It would be helpful to know what the intended semantics is. I don't know whether any of the following are bugs, but they look strange anyway.Starting from:
I can do either
intros
orintros HA HB
, which work as expected:intros
makes up a fresh hypothesis name, andintros HA HB
uses the names I gave. But the following are strange:Conflicting names (I guess that's ok):
Too many names (I guess that's ok, although for script robustness I would rather have a failure here):
Giving "not enough names" works fine (later names are picked by the system), except if the name given are H1, H2...:
(notice that two hypotheses now have the same name)
The text was updated successfully, but these errors were encountered: