Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Establish conventions for macro internals #22607

Copy link
Copy link
@alexcrichton

Description

@alexcrichton
Issue body actions

We should establish conventions for how to expose the implementation details of macros as parts of the public API of a crate. Currently we have two "schemes"

  • Prefix the name with __ example
  • Liberal use of #[doc(hidden)] example

It would be nice to standardize on the convention here as most of these internals "we'd really rather not expose". I personally like the double-underscore-prefix-plus-#[doc(hidden)] strategy but others may feel differently!

Nominating, this may tidy up some of our apis in std.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.