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
Synopses should have numbered headers #566
Comments
Question: Should all synopses appear at the top-most level, as a sibling to "General", as we currently do with the containers library? Or is it appropriate to keep them within their respective subsections (and use For example, consider [diagnostics]. We could either list the synopses of I'm mildly in favour of the latter approach, since we'd otherwise be left with text that wouldn't have a section any more (such as the text after the |
@tkoeppe: Ping. What should we do with all the remaining |
Partially addresses cplusplus#566.
Partially addresses cplusplus#566.
Partially addresses cplusplus#566.
Remove now-empty 'Overview' sections. Partially addresses cplusplus#566.
Remove now-empty 'Overview' sections. Partially addresses #566.
Partially addresses cplusplus#566.
Partially addresses cplusplus#566.
Partially addresses cplusplus#566.
Also remove use of \synopsis for class template definitions. Partially addresses cplusplus#566.
Also remove use of \synopsis for class template definitions. Partially addresses #566.
[res.on.functions] Do not use \synopsis for emphasis. Fixes cplusplus#566.
[res.on.functions] Do not use \synopsis for emphasis. Fixes #566.
Following PR 560, @zygoloid noticed that there are still several synopses that don't have numbered headers (e.g. strings, algorithms). Uses of
\synopsis
should be replaced with:See also #542.
The text was updated successfully, but these errors were encountered: