Skip to content

deprecated lint should not warn within a deprecated module #16490

Closed
@aturon

Description

@aturon

The stability lint was recently changed to warn on use of deprecated items even when they are defined in the same crate. An unintended consequence is that, when an entire module is deprecated, the body of the module will warn on every use of items defined within it.

We should change this behavior, but it's not entirely clear what the rule should be or how to implement it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions