Rust Docs should not include internal crates

[wycats]

For example, when I was originally searching for serialize (in the wrong place, I suppose), I got a bunch of internal results. Link to the search.

[wycats]

I also feel that we should not have duplicate core and std entries.

[aturon]

Paring down what shows up in rustdoc is going to be a key step for 1.0 readiness. Nominating P-high, 1.0 polish.

triage: I-nominated ()

[richo]

cc me, ideally there'll be a frob to still specify the old behaviour. rustdoc has been invaluable when I'm spelunking for something.

[aturon]

@richo Yes indeed, it's important that this is still available in some form for people who want to hack on Rust itself.

[bombless]

I also feel that we should not have duplicate core and std entries.

+1

[tomjakubowski]

I swear there was a pretty old open issue for this already but I can't find it. Also cc #22083 which is important and related.

[tomjakubowski]

I also feel that we should not have duplicate core and std entries.

This would be addressed for the common Rust user by just removing internal crates (including core) from the docs for the release channel. Nightly users, or at least users of core, and people working on the Rust distribution itself are likely going to want to retain item duplication between core and std because it matters to them.

If you initiate your search from std/core then entries in those crates will come first anyway.

[tomjakubowski]

Duplicate of #21297

[emberian]

I'll have a PR for this soon (it's testing)