-
Notifications
You must be signed in to change notification settings - Fork 694
Abbreviations don't add printing rule when still qualified #20816
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
Conversation
@JasonGross apparently, fiat-crypto was relying on the bug in its output test, could you please prepare an overlay |
The failing tests look kinda bad no? < fun var : API.type -> Type =>
---
> fun var : type (Language.Compilers.base.type.type base) -> Type => -fun x : positive => (- Z.pos x~0 + 0)%Z
+fun x : positive => (- Zpos x~0 + 0)%Z |
Not sure we want this change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a bad idea, and seems to me to be removing a feature rather than fixing a bug. At the very least, it should be possible to indicate at declaration time whether am abbreviation is meant to escape the scope of the module. (Note that an abbreviation whose printing does not escape the module scope is already possible to emulate by having an only parsing abbreviation + an only printing notation that is not an abbreviation.)
That's definitely not an acceptable workaround. That being said, the fix indeed seem more complicated than initially expected. We may need to think a bit more about this whole abbreviation locality story. |
Rocq call: try having standard local/export/global behaviours for the printing rule (with export as default, and current behaviour is close to global) |
CI confirms this is indeed the case |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have not looked at code changes, but the behavior change seems good
@coqbot merge now |
@proux01: Please take care of the following overlays:
|
Fix #20668
Overlays (to be merged before the current PR)
Overlay (to be merged in sync with the current PR)