Tracking issue for edition-specific preludes

[m-ou-se]

This is a tracking issue for the edition-specific preludes.

RFC: rust-lang/rfcs#3114

Feature gates: prelude_2015, prelude_2018, and prelude_2021.

Public API

// std::prelude and core::prelude

pub mod rust_2015 {
    pub use super::v1::*;
}

pub mod rust_2018 {
    pub use super::v1::*;
}

pub mod rust_2021 {
    pub use super::v1::*;
    pub use crate::iter::FromIterator;
    pub use crate::convert::{TryFrom, TryInto};
}

Steps / History

• RFC: A new prelude for the 2021 edition (trait-only edition) rfcs#3114
• Final commenting period (FCP): A new prelude for the 2021 edition (trait-only edition) rfcs#3114 (comment)
• Add prelude::rust_* and pick one depending on the edition: Edition-specific preludes #82217
• Add the new traits to prelude::rust_2021: New prelude #85687
• Implement migration lint: Tracked in Migration lints for 2021 prelude #84594
• Stabilize the preludes and update the documentation: Stabilize {std, core}::prelude::rust_*. #86294

Unresolved Questions

• None yet.

[SimonSapin]

Stabilize the preludes and update the documentation.

Is there something prelude-specific to stabilize besides allowing any use of the 2021 edition on Stable?

[m-ou-se]

@SimonSapin The modules std::prelude::rust_* are currently unstable. So stabilizing them will make it possible ot refer to those explicitly. Automatically importing the 2021 prelude on edition 2021 is already stable (except that that edition itself isn't stable yet).