Skip to content

[lib] Subheadings in class descriptions #1242

Closed

Description

@jensmaurer

We have both:

  • Class template blah
    -- blah constructors
    (etc)

and

  • Class template blah
    -- Construction and assignment [note: omitting "blah" in subordinate headings]
    (etc)

[basic.string] is an example for the former, [string.view.template] is an example for the latter.

Which way is the "right" way?

Activity

  1. added
    decision-requiredA decision of the editorial group (or the Project Editor) is required.
    on Dec 14, 2016
  2. jensmaurer commented on Mar 2, 2017

    @jensmaurer
    MemberAuthor

    Editorial meeting consensus: Do not repeat a parent heading item in subordinate headings.

  3. removed
    decision-requiredA decision of the editorial group (or the Project Editor) is required.
    on Mar 2, 2017
  4. added this to the milestone on Apr 5, 2017
  5. tkoeppe commented on Apr 2, 2018

    @tkoeppe
    Contributor

    @jensmaurer: What about [container.node]?

  6. jensmaurer commented on Apr 2, 2018

    @jensmaurer
    MemberAuthor

    @tkoeppe: [container.node] is odd. It specifies an exposition-only class node_handle, which need not exist under this name. Everywhere else in the vicinity, we specify requirements on classes or class templates by specifying the valid operations on them, instead of showing a class synopsis.

    I'd like to point out that the superordinate heading says "Node handles" and the subordinate headings say "node_handle", which is not exactly a repetition (although quite close).

  7. tkoeppe commented on Apr 2, 2018

    @tkoeppe
    Contributor

    @jensmaurer: Yeah, that's true. Not sure what to do here. @zygoloid: Opinions?

    My primary goal here is to get rid of a bold-italic-teletype font requirement, which we cannot satisfy :-)

  8. zygoloid commented on Apr 2, 2018

    @zygoloid
    Member

    I'm happy with removing node_handle from these headings, as they are not really describing members of some class named node_handle; rather, they're describing members of the exposition-only notion of a "node handle". Done in 2fcacf3.

  9. JohelEGP commented on Jun 27, 2018

    @JohelEGP
    Contributor

    Do you have a stance on the repetition in the headers' synopsis? That repetition might provide some context that's implicitly available in the subclauses for being nested.

  10. jensmaurer commented on Jun 28, 2018

    @jensmaurer
    MemberAuthor

    @JohelEGP, I don't understand the question. Header synopses usually say "Header <blah> synopsis", and that doesn't mention a class name.

  11. JohelEGP commented on Jun 28, 2018

    @JohelEGP
    Contributor

    I mean the line comments like this:

        // [time.duration], class template duration
        template<class Rep, class Period = ratio<1>> class duration;
  12. jensmaurer commented on Jun 28, 2018

    @jensmaurer
    MemberAuthor

    @JohelEGP, those comments quote the subclause heading, so those seem fine.

  13. jensmaurer commented on Nov 27, 2018

    @jensmaurer
    MemberAuthor

    This should be complete now.

  14. added
    bigAn issue causing a large set of changes, scattered across most of the text.
    on Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bigAn issue causing a large set of changes, scattered across most of the text.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions