Add separators between parts of API documentation #1384
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds horizontal lines as separators between examples, functions, classes in the API documentation. Especially in cases where e.g. an example, variable, and
versionadded
directive are grouped together, it can sometimes be hard to see how they are grouped. It's easy to mistake that the example might belong to the next item.This also moves the
async_rw_mutex
example up to the top of the section, before the API documentation. This way it serves as an overview before the details of the API documentation. We do the same in thepika/init.hpp
section.