Pre-RFC: documentation comments after code

[Nemo157]

See also

Any interest in same-line Doc-Comments?

In C/C++, I would often use documentation-after-member (as supported by Doxygen) because it makes better use of available screen space (and thus improves comprehension by reducing load on the reader’s working memory). As an example, consider this example usage from a hypothetical symbolic math library: /// Kind of operation performed by a binary expression. enum BinaryOperation { SUM, ///< addition PRODUCT, ///< multiplication POWER, ///< exponentiation LOG ///< loga…

which covers just the enum variants (and presumably struct fields) part of this.