-
Notifications
You must be signed in to change notification settings - Fork 631
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
Rename mlg grammar nonterminals to make documented and mlg grammars more consistent #13219
Conversation
2de10a1
to
c1d0472
Compare
This comment has been minimized.
This comment has been minimized.
f477ac7
to
6850f7c
Compare
Rebased. Do we need any others to review this? |
I believe we can go. Merging tomorrow (if no comments by then and if I don't forget). |
plugins/syntax/g_numeral.mlg
Outdated
| #[ locality = Attributes.locality; ] [ "Numeral" "Notation" reference(ty) reference(f) reference(g) ":" | ||
ident(sc) numnotoption(o) ] -> | ||
|
||
{ warn_deprecated_numeral_notation (); | ||
vernac_numeral_notation (Locality.make_module_locality locality) ty f g (Id.to_string sc) o } |
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.
Wait a minute. This PR removes the deprecated Numeral Notation
command but this command was only deprecated in 8.13, which is not released yet.
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.
OK, waiting.
By the way, won't it be too much of a burden for users to change from Numeral
to Number
? (Or maybe the changes are already clearly accepted upstreams?)
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.
By the way, won't it be too much of a burden for users to change from
Numeral
toNumber
? (Or maybe the changes are already clearly accepted upstreams?)
That's a fair question. There has been a bit of a debate after the PR changing this was merged. See #12979 (comment). IMHO for this kind of cosmetic change, the solution is to make the deprecation period sufficiently long (a bit like the Ocaml
vs OCaml
value for Extraction Language
which was changed and deprecated in 8.8 but only removed in 8.13).
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.
Yes, this is somehow the question. Is the added value of the change worth the burden (but again, if the change is already validated by the users, it does not matter)?
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.
My mistake during rebasing, now fixed.
The PR otherwise looks good to me (I reviewed the changes to the refman in particular). |
Ah, I realize that changing
|
I believe that the probability that this undocumented symbol was used is close to 0. So, option 1 seems reasonable to me. |
OK. I'm making one more small fix, should be done shortly. |
The job library:ci-fiat_crypto_legacy has failed in allow failure mode |
It seems like the f-c-l job should have been restarted automatically?
cc @Zimmi48 ? |
OK, made my little fix (using |
Indeed, like @JasonGross said (thanks for reporting BTW), this is an unrelated failure that should have been restarted automatically (I have identified the issue). Just to be sure, I'm manually restarted the job. |
typ_param -> ltac2_typevar, tac2expr -> ltac2_expr
Rebased. |
Thank you, sir! |
While updating the syntax in the documentation, we (primarily me and @Zimmi48) found that many of the
mlg
nonterminal names were not good enough for use in the documentation, so we chose better names. This PR updates the mlgs so that they use most of these names. This will make it less confusing for developers to relate the grammar in the manual to the mlg files. (I frequently got confused by the different names even though I'm acutely aware that there are differences in the names.)There is no functional change here other than that the
Print Grammar
command output may show some of the changed names. Global variables for nonterminals defined inmli
files that were renamed were made equal to the new variables and deprecated to avoid breaking external plugins that may rely on those variables.Perhaps @herbelin is willing to do the review?
"A rose by any other name would smell as sweet"