Docs: Hide nightly-only messages on doc.rust-lang.org/nightly-rustc

[Havvy]

When reading the nightly-rustc docs, all the yellow boxes saying they're experimental is entirely noise. It'd be nice to remove them.

[Havvy]

I'm putting both T-Doc and T-Rustdoc, but I'm not sure which teams this falls under.

[steveklabnik]

This is a deliberate design decision to inform people of APIs that may exist in the future, and point to where you can request stabilization. T-rustdoc may or may not want to reconsider this, though, so I won’t close just yet.

…

On Sep 29, 2018, at 5:47 PM, Ryan Scheel ***@***.***> wrote: I'm putting both T-Doc and T-Rustdoc, but I'm not sure which teams this falls under. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Havvy]

That makes sense on core, std, and alloc, but rustc_nightly is all implementation details. It's placed on literally everything on https://doc.rust-lang.org/nightly/nightly-rustc/syntax/parse/struct.ParseSess.html#method.buffer_lint when there's no reason to expect to be able to use the struct at all in stable Rust. A top level notification that it's the internal docs might not go amiss, but this is a bit excessive.

[Mark-Simulacrum]

I think it makes more sense to stop shipping nightly-rustc as part of the stable and beta toolchains, presuming we do so today.

Having said that, I could see the usecase for telling rustdoc "this set if features is enabled already" such that we could whitelist rustc_private for the compiler docs.