-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
impl Deref for EndianSlice appears in std docs #74672
Comments
rust/src/librustdoc/clean/inline.rs Lines 349 to 355 in e24a017
Maybe this should also skip the impl if there is no 'stability' attribute? https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/query/queries/struct.lookup_stability.html, https://doc.rust-lang.org/nightly/nightly-rustc/rustc_attr/builtin/struct.Stability.html |
This is the default for everything not in the standard library. So it seems like the standard library needs special casing here. Maybe as simple as |
Doesn't gimli get everything marked as unstable behind the rustc_private feature gate through a rustc flag? |
MCVE: https://github.com/lzutao/rustdoc-traits-bugs |
…n514 Ignore rustc_private items from std docs By ignoring rustc_private items for non local impl block, this may fix rust-lang#74672 and fix rust-lang#75588 . This might suppress rust-lang#76529 if it is simple enough for backport.
…n514 Ignore rustc_private items from std docs By ignoring rustc_private items for non local impl block, this may fix rust-lang#74672 and fix rust-lang#75588 . This might suppress rust-lang#76529 if it is simple enough for backport.
…n514 Ignore rustc_private items from std docs By ignoring rustc_private items for non local impl block, this may fix rust-lang#74672 and fix rust-lang#75588 . This might suppress rust-lang#76529 if it is simple enough for backport.
impl Deref for EndianSlice
appears on the current nightly'sstd::ops::Deref
documentation page, even though it's not part of the (public) standard libraries. This appears to begimli::read::EndianSlice
, so maybe related to #73441, cc @alexcrichton.Noticed by @rijenkii (assuming they use the same handle here and discord, if not, sorry 😳)
The text was updated successfully, but these errors were encountered: