We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Updated Specification Style Guidelines (markdown)
Add source code formatting guides.
Don't suggest "Effects: Behaves the same as: ..."
Give an example of the disallowed form "Effects: Equivalent to: return x."
Update style rules to indicate that "shall" is usually a requirement at the program level, not at the implementation level (the implementation-level requirement is for a diagnostic)
Add "Returns" element style.
Move some wording guidelines from https://github.com/cplusplus/LEWG/blob/master/library-design-guidelines.md
Let statements in function descriptions
Add references to library conventions/rules in the standard itself; thanks to Beman for the suggestion!
Remove spurious paren
add implicitly generated special member functions bit based on suggestion from Beman