Repository navigation
docs: add a reference overview that groups the API by purpose - #417
TheLingeringWill wants to merge 4 commits into
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 4
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
|
[Low impact] The PR appears safe to merge; no actionable issues were found.
|
|
An automated preview of the documentation is available at https://417.corosio.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-11-13 14:33:35 UTC |
|
GCOVR code coverage report https://417.corosio.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-11-13 14:52:07 UTC |
Move TCP after Name Resolution, since its prose names the resolver. Fix claims that did not match the headers: error lists only Corosio's own codes, file_base's seek origins apply to stream_file only, and connect_pair uses a temporary path on Windows. Note the io_uring backend, the native socket options, and the OpenSSL system category.
Part of cppalliance/capy#416.
The Boost review asked that the reference break the API into sections by purpose,
"similar for Corosio". cppalliance/capy#484 did this for Capy. This does the same for
Corosio, using only what MrDocs already produces: its tagfile and the
cpp:macro. Thegenerated index is unchanged, and is now named "Index by Kind", as in Capy.
Changes
doc/modules/ROOT/pages/reference-overview.adoc(new): fifteen sections:Each section has a short intro that links the guide pages teaching it, and a
Kind | Namestable. The tables list every symbol on the generatedboost::corosioand
socket_optionindex pages once (114 names), except namespaces and operators, ascpp:links.nav.adoc: "Reference" now opens the overview, with one child per section and an"Index by Kind" child for the generated index.
glossary.adoc: the See Also section links both pages.STYLE_GUIDE.mdE3: records the page, and that an API change must update it in thesame pull request.
The test tools in
boost::corosio::testare not in the generated reference, because MrDocsparses only
<boost/corosio.hpp>andnative/native.hpp. The overview says so and linksthe Testing section instead.