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
Fix #18657: "Include" objects were not always taken into account in Search #18662
Fix #18657: "Include" objects were not always taken into account in Search #18662
Conversation
That was quick! Thank you very much. The duplication is unfortunate but this can be treated at another time. I'm not even sure there is a better solution; after all the lemmas are there with two names so this behaviour is expected. |
@coqbot run full ci |
Indeed, nothing specific to the current PR. Still, this duplication remains one of the painful issues of |
Probably, the simplest would be to ensure that the |
There are also |
If I'm not mistaken, the impact of Oh, maybe a simple way is to display only the names whose user name is the same as the canonical name! That could be tried. |
Hum, if we do that, printing only the original "canonical" constants, then this means printing the oldest one, which is probably not the intended, shortly-named, one. On the other side, if we hide re-aliased module, that's not fully satisfactory either. If we have |
@coqbot merge now |
The fix was simple.
Note that this may imply duplication of results: in the case of a module, we have a result both with the original name and with the included names. But this is a phenomenon which is not only about
Include
. E.g.,Module M := N
has similar consequences.Fixes / closes #18657