Unit is documented as a template. The availability of specializations is noted, since each specialization may have different members. Documenting them all on one page would be fine (as cppreference.com does) or on separate pages (as Doxygen seems to insist on doing).
The comments on each specialization are available where the specialization is documented.
Actual Results
In the top-level view, Unit appears three times, once as a template, and twice as a non-template:
All three link to the same place, #Unit/Unit. It looks like this:
As you can see,
It isn't presented as a template at all.
The presence of full and partial specializations is not indicated (which I suppose makes sense, if it isn't a template).
It has the doc comment from the second full specialization only -- the others appear to have been lost.
In case you're curious, if you add members to the specialization whose doc comment appears (Unit<double>) they appear in the docs. Members added to the base template or other specializations are dropped.
Encountering several specializations (full or partial) of a class template mangles the documentation results for the template.
Found in b3fc442786b219746cf6487fc606ef1a77e94a90
Input
Expected Results
Unit
is documented as a template. The availability of specializations is noted, since each specialization may have different members. Documenting them all on one page would be fine (ascppreference.com
does) or on separate pages (as Doxygen seems to insist on doing).The comments on each specialization are available where the specialization is documented.
Actual Results
In the top-level view,
Unit
appears three times, once as a template, and twice as a non-template:All three link to the same place,
#Unit/Unit
. It looks like this:As you can see,
In case you're curious, if you add members to the specialization whose doc comment appears (
Unit<double>
) they appear in the docs. Members added to the base template or other specializations are dropped.