-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
rustdoc bug: page "ByteStr" is outright wrong: it shows methods for [MaybeUninit<...>] #137083
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Duplicate of #24686 |
4 tasks
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Mar 24, 2025
Rollup merge of rust-lang#138574 - lolbinarycat:rustdoc-deref-24686-v2, r=GuillaumeGomez rustdoc: be more strict about "Methods from Deref" fixes rust-lang#137083 fixes rust-lang#24686 Currently done: * [x] fix `render_assoc_items_inner * [x] fix sidebar logic * [x] port test from rust-lang#137564 * [x] add test for sidebar items Note that this does not yet fix the sidebar logic.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rustdoc bug: page
ByteStr
is outright wrong: it shows methods for[MaybeUninit<...>]
Information on page https://doc.rust-lang.org/nightly/std/bstr/struct.ByteStr.html is currently totally wrong.
After inherent methods we see "Methods from
Deref<Target = [u8]>
". But then instead of methods of[u8]
, we actually see methods of[MaybeUninit<T>]
!!! Immediately after header "Methods fromDeref<Target = [u8]>
" we see methodwrite_copy_of_slice
, which is actually[MaybeUninit<T>]
method!@rustbot label: +T-rustdoc
The text was updated successfully, but these errors were encountered: