-
Notifications
You must be signed in to change notification settings - Fork 643
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
More parsing/printing notation/abbreviation consistency for mixed terms and pattern #12099
More parsing/printing notation/abbreviation consistency for mixed terms and pattern #12099
Conversation
I'm turning this PR in draft mode because of the dependency. If you expect feedback from some specific groups of maintainers, please say so. With PR dependencies, try to always use the draft mechanism, otherwise the code owner mechanism is generating review spam. |
Dear PR author(s) and contributors, it seems to us this PR may need additional work beyond the 8.12 branching deadline on May 15th. We are thus removing the 8.12+beta1 milestone; please retarget as appropriate, and also consider updating labels to reflect current status, etc. We apologize in advance if we misunderstood the PR status. |
It depends on #8808 which depends on @mattam82 who seems to have other priorities these days. I just asked @ejgallego instead. |
fe27652
to
d292b29
Compare
d292b29
to
3dd380b
Compare
3dd380b
to
f8e26c3
Compare
@ejgallego: Is it asking a lot to possibly review this PR? |
Rebased and dependencies merged. |
f8e26c3
to
8ec6aae
Compare
@herbelin I'm reviewing, sadly the CI didn't run due to the limits, please rebase and push. |
8ec6aae
to
6b8e2d7
Compare
@herbelin unfortunately this got a conflict :S please rebase, and hopefully we can merge. |
…tterns. Currently, global references in patterns used also as terms were accepted for parsing but not for printing. We accept section variables for both parsing and printing. We reject constant and inductive types for both parsing and printing. Among other, this also fixes a hole in interpreting variables used both patterns and terms: the term part was not interpreted.
This will allow for instance to check the status of a variable name used both as a term and binder in notations.
…ers in notations. This also includes tests for abbreviations.
6b8e2d7
to
6521021
Compare
OK, rebased. |
Failure are unrelated, merging. @coqbot: merge now |
@ejgallego: You can't merge the PR because it hasn't been approved yet. |
@coqbot: merge now |
@ejgallego: Could not find merge comment. cc @Zimmi48 |
@coqbot: merge now (sudo) |
@ejgallego: Could not find merge comment. cc @Zimmi48 |
Kind: bug fix / cleanup
Depends on #8808 (now merged).
This is a continuation of #8808 about mixed binders and terms in notations and abbreviations. It ensures consistency of printing and parsing for both notations and abbreviations in the different possible configurations (see test-suite file
Notations4.v
).For the record, the typical application of such mixed terms and binders notations is the "maximal group such that" used in MathComp or the "forcing" modality:
It does not fix the printing order issue that #9311 is trying to fix.
Corresponding documentation was added in Extending support for mixing binders and terms in abbreviations #8808.