-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Public unstable feature="inplace_iteration" APIs without a tracking issue #85373
Copy link
Copy link
Closed
Closed
Copy link
Labels
B-unstableBlocker: Implemented in the nightly compiler and unstable.Blocker: Implemented in the nightly compiler and unstable.Libs-SmallLibs issues that are considered "small" or self-containedLibs issues that are considered "small" or self-containedT-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
B-unstableBlocker: Implemented in the nightly compiler and unstable.Blocker: Implemented in the nightly compiler and unstable.Libs-SmallLibs issues that are considered "small" or self-containedLibs issues that are considered "small" or self-containedT-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.
The
SourceIterandInPlaceIterableunstable traits are public, so they and theirimpls show up in docs. For example https://doc.rust-lang.org/1.52.1/std/iter/trait.InPlaceIterable.html. However unlike other unstable public APIs, there is no link to a tracking issue.These traits were added by @the8472 in #70793. It’s not clear from the PR’s description if the traits are intended as private implementation details of the standard library that are only technically
pubso that they can be used across multiple standard library crates, or if they are intended as a new public API with a possible path to eventual stabilization.Source definitions of the traits and
impls should either have#[doc(hidden)]attributes added, or a tracking issue should be filed and the#[unstable]attributes modified to point there.