You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: move template specializations and deduction guides off parent scope page
Class template specializations, function template specializations, and
deduction guides used to share the enclosing scope's listing with their
primary template. Users have repeatedly reported this as confusing: `A`
and `A<int>` appearing side by side in the namespace index reads as if
they were independent siblings, and a primary's variants were nowhere on
its own page.
Specializations now appear in a dedicated "Specializations" section on
the primary's documentation page, and deduction guides in a "Deduction
Guides" section on the deduced class's page. The parent scope's listing
carries only the primary itself. An orphan specialization (one whose
primary has been excluded from extraction) stays in the parent's listing
so the index can still reach it.
The relationship is stored in the corpus: each primary record or
function template carries the IDs of its specializations (and, for class
templates, of its deduction guides), and each specialization carries an
`IsListedOnPrimary` flag. The lists are populated by a finalizer pass
and exposed via reflection, so the XML output gains matching
`<specializations>`, `<deduction-guides>`, and `<is-listed-on-primary>`
elements and the DOM/Handlebars layer renders the new sections through
plain field access.
Closes issue #1154.
0 commit comments