-
Notifications
You must be signed in to change notification settings - Fork 772
Inconsistent punctuation in Table Associative container requirements #760
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
Comments
Yes, absolutely - make a PR! :-) |
Those tables don't always start sentences with uppercase letters either. |
See #328 for addressing parts of the inconsistencies. |
See #4460 for dismantling the requirements tables. Check the punctuation again after this has landed. |
Auditing punctuation following the dismantling of the requirements tables: Result: and Complexity: elements are inconsistent in their use of a period, or not. Effects: elements consistently either close with a period, or do not use period for the form: equivalent to All other elements are consistently well-formed sentences end with a period. |
Uh oh!
There was an error while loading. Please reload this page.
Some entries in the "Assertion/note pre-/post-condition" column of [associative.reqmts] Table 102 - "Associative container requirements" end with a period while others do not. I propose having them all end with periods.
Same for [unord.req] Table 103 - "Unordered associative container requirements (in addition to container)", and probably other library tables as well.
The text was updated successfully, but these errors were encountered: