Skip to content

Tracking issue for RFC #2145: Type privacy and private-in-public lints  #48054

Closed
@aturon

Description

@aturon

This is a tracking issue for the RFC "Type privacy and private-in-public lints " (rust-lang/rfcs#2145).

Steps:

Unresolved questions:

  • It's not fully clear if the restriction for associated type definitions required for
    type privacy soundness, or it's just a workaround for a technical difficulty.

  • Interactions between macros 2.0 and the notions of reachability / effective
    visibility used for the lints are unclear.

Metadata

Metadata

Assignees

Labels

A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.A-visibilityArea: Visibility / privacyB-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-design-concernsStatus: There are blocking design concerns.S-tracking-needs-summaryStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.T-langRelevant to the language team, which will review and decide on the PR/issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions