Repository navigation
Tracking issue for RFC #2145: Type privacy and private-in-public lints #48054
Description
This is a tracking issue for the RFC "Type privacy and private-in-public lints " (rust-lang/rfcs#2145).
Steps:
- Implement the RFC (cc @petrochenkov )
- Adjust documentation (see instructions on forge)
- Stabilization PR (see instructions on forge)
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
Area: Lints (warnings about flaws in source code) such as unused_mut.Area: Visibility / privacyBlocker: Approved by a merged RFC but not yet implemented.Category: An issue tracking the progress of sth. like the implementation of an RFCStatus: There are blocking design concerns.Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation.Relevant to the language team
Activity
Auto merge of #56878 - petrochenkov:privdyn, r=arielb1
Aaron1011 commentedon Aug 24, 2019
@rustbot claim
Aaron1011 commentedon Aug 24, 2019
@petrochenkov: Oops - I didn't mean for that to un-assign you.
Is there a way to prevent these lints from becoming insta-stable? Would it make sense to put them behind a feature gate?
Aaron1011 commentedon Aug 24, 2019
Perhaps we could only fire the lints if an unstable compiler flag (maybe
-Z type-privacy-lints) is passed? This would still make the lint names insta-stable, though.Allow using #[pin_project] type with private field types
Allow using #[pin_project] type with private field types
Allow using #[pin_project] type with private field types
Allow using #[pin_project] type with private field types
41 remaining items
Auto merge of rust-lang#113126 - Bryanskiy:delete_old, r=petrochenkov
Auto merge of #113126 - Bryanskiy:delete_old, r=petrochenkov
petrochenkov commentedon Jan 19, 2024
This issue should be closed by #120144.
Two follow up issues about improving the effective visibility tables
Auto merge of #113126 - Bryanskiy:delete_old, r=petrochenkov
Rollup merge of rust-lang#120144 - petrochenkov:unty, r=davidtwco
Unrolled build for rust-lang#120144
Auto merge of #102026 - Bryanskiy:resolve_update, r=petrochenkov
Auto merge of #102233 - petrochenkov:effvis, r=jackh726
Auto merge of #102026 - Bryanskiy:resolve_update, r=petrochenkov
Auto merge of #102233 - petrochenkov:effvis, r=jackh726
Auto merge of #113126 - Bryanskiy:delete_old, r=petrochenkov