Tracking issue for `alloc::prelude`

[SimonSapin]

Its stability was separated from that of the alloc crate in #58933.

CC rust-lang/rfcs#2480

[roblabla]

The alloc_prelude feature gate seems to be broken: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=808681d68a06487853e5d2d3416fd332 compiles and runs just fine without specifying the #![feature(alloc_prelude)] feature gate.

[SimonSapin]

This is a case of #15702.

(The documented example use alloc::prelude::v1::*; does require the feature gate.)

[LukasKalbertodt]

What exactly is blocking stabilization? Any unresolved questions? Just gaining experience with it?

[SimonSapin]

I think there was a question of how useful this is, since unlike core::prelude or std::prelude this isn’t injected automatically in any crate. Feedback from projects who use it despite this or would like to use it despite this would be helpful.