This was found while building docs for Boost.Capy.
Consider the annotations in https://github.com/cppalliance/capy/blob/develop/include/boost/capy/write.hpp#L25
It has two lists (two sets of @li tags):
- One in the general prose section,
- The other under
@return sections.
Now observe the outcome: https://master.capy.cpp.al/capy/reference/boost/capy/write.html
The first list is rendered correctly. The other appears under section "Cancellation" rather than under section "Returns".
It looks like @li elements are always identified as part of general prose (apparently @par belongs in there also), and never as part of @return.
I can imagine a reply "works as designed", but in that case I would request a way to put lists inside known section elements, like @return.
This was found while building docs for Boost.Capy.
Consider the annotations in https://github.com/cppalliance/capy/blob/develop/include/boost/capy/write.hpp#L25
It has two lists (two sets of
@litags):@returnsections.Now observe the outcome: https://master.capy.cpp.al/capy/reference/boost/capy/write.html
The first list is rendered correctly. The other appears under section "Cancellation" rather than under section "Returns".
It looks like
@lielements are always identified as part of general prose (apparently@parbelongs in there also), and never as part of@return.I can imagine a reply "works as designed", but in that case I would request a way to put lists inside known section elements, like
@return.