Skip to content

Replacing sentences for references by a Bibliography section for keywords #65886

@dorfsmay

Description

@dorfsmay

In the stdlib, at the end of each keyword description, authors add a small sentence with links to reference material.
Here are the six first ones appearing in the keyword file:

/// For more information on what `as` is capable of, see the [Reference]

/// For more detail on `const`, see the [Rust Book] or the [Reference]

/// For more information, take a look at the [Rust Book] or the [Reference]

/// For more information on FFI, check the [Rust book] or the [Reference].

/// For more information on the various types of functions and how they're used, consult the [Rust

/// More details on the functionality shown can be seen at the [`IntoIterator`] docs.

Beside the fact that they are inconsistent ("for more information", "for more details", "more details on", "see", "take a look", "check", "can be seen at"), the style itself feels heavy and goes against publishing standards. References are typically listed either in a "Reference list" or a "Bibliography".
See https://intranet.birmingham.ac.uk/as/libraryservices/library/referencing/icite/harvard/referencelist.aspx.

The two advantages of adopting this style immediately obvious:

  • consistent style, not only between keywords, but with sites widely used such as Wikipedia
  • reduce cognitive load for athors, trying to make up a small sentence to introduce references, especially when wanting to quote more than one.

I propose that we use a "Bibliography" section and use it for bot references and additional material pertinant to the subject.

Here's an example of an existing page, in its current version:
current

Replacing the "For more information..." sentence with a Blbliography section:
with_bibliography

Comments will be appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsC-enhancementCategory: An issue proposing an enhancement or a PR with one.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions