-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Stability checker doesn't recurse down reexports properly #21905
Copy link
Copy link
Open
Labels
A-stabilityArea: `#[stable]`, `#[unstable]` etc.Area: `#[stable]`, `#[unstable]` etc.C-bugCategory: This is a bug.Category: This is a bug.F-staged_api`#![feature(staged_api)]``#![feature(staged_api)]`T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
A-stabilityArea: `#[stable]`, `#[unstable]` etc.Area: `#[stable]`, `#[unstable]` etc.C-bugCategory: This is a bug.Category: This is a bug.F-staged_api`#![feature(staged_api)]``#![feature(staged_api)]`T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
stability.rs:
test.rs:
#[unstable]is inherited through mods (only#[stable]isn't inherited). However, in this particular case, the inheritance doesn't cross the reexport.A more concrete example is the
hash_statemodule. Chris fixed the stability of its items in this PR, however the module itself was private and reexported as an#[unstable]module before the PR. Yet, usage of items within thehash_statemodule were broken before the PR.This seems wrong,
#[unstable](and the others, except#[stable]) should be inherited downpub uses.cc @brson