We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Result of searching "// hash" shows...
[vector.syn] // hash support [unord.map.overview] // hash policy: [unord.set.overview] // hash policy: [unord.multimap.overview] // hash policy [unord.multiset.overview] // hash policy: [thread.thread.id] // Hash support
Well, there are at least 2 problems.
//
Not sure if there has been already some rules about styles in comments, esp. in synopses. (Nonetheless, the examples above seem to be unintended.)
The text was updated successfully, but these errors were encountered:
I think we agreed we usually want:
// \ref{...}, hash support
Additional punctuation was deemed unnecessary, as was capitalization.
Sorry, something went wrong.
[lib] Harmonize introductory comments in synopses
b2eeec5
Even if no section reference is given, make them lowercase and remove trailing colons. Fixes cplusplus#1709.
jensmaurer
No branches or pull requests
Result of searching "// hash" shows...
Well, there are at least 2 problems.
//
?Not sure if there has been already some rules about styles in comments, esp. in synopses. (Nonetheless, the examples above seem to be unintended.)
The text was updated successfully, but these errors were encountered: