Skip to content

M-NO-GLOB-REEXPORTS is excessively broad #4

@sandersaares

Description

@sandersaares

It is perfectly fine to re-export types within a crate for filesystem-structural reasons, if we want to split some types off to a separate file. Glob re-exports should only be discouraged for cases where the re-exported item is already public via a different path (e.g. part of a different crate or via another public module).

For filesystem-structural reasons, no review of what is being re-exported is expected, either - each file should have clear pub or lack thereof on its types, indicating what is part of the public API. As an alternative UX, generated documentation can be used for review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    issueRelates to a issue on an existing guideline.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions