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
Check element order programmatically and presubmit #3677
Comments
Partially addresses cplusplus#3677
My script found the following (at commit b8e16d5):
I haven't checked them yet but the |
The commit-id link to your script is wrong. Please fix. |
It's not a link to the script, it's the revision I tested using the script. The script itself is in the commit referenced above: jwakely@523fe59 |
Ah, sorry for the confusion. (It seems the script source code doesn't scale; its size is O(n^2/2) or so where n is the number of specification elements.) |
This script scales better:
and delivers more output:
|
I was about to file an issue on generally inconsistent ordering of constraints, mandates, and preconditions (expects) in the current draft, that probably arose after applying a number of papers for Prague, but figured I should defer to this ticket? Probably worth running that script again to see if the problem is getting worse. Do we have any plans to resolve the reported orderings? |
I'm willing to post a pull request that fixes the orderings here, at least those that can be fixed by simple reordering. |
I have limited net access this weekend, but after that yes |
Thanks; I just want to avoid repeated merge conflicts. |
Remaining cases:
|
Editorial meeting: Allow for a comment marker on \begin{itemdescr} such as "% CHECK: noordering" to disable the check. Then, activate the script. |
The specification elements (Remarks":, "Preconditions:, etc.) should appear in a specific, fixed order; we could try and check that this is the case programmatically and run this check as part of the presubmit checks.
The text was updated successfully, but these errors were encountered: