-
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
Some internal rustdoc links broke #81037
Comments
@lzutao those warnings are denied on CI, so they shouldn't ever be happening. How did you compile the standard library? |
I pass |
I still can't reproduce:
Can you please post the full command line you're using? |
If that helps, sure: STD_DATE=$(rustc -Vv | grep commit-date | awk '{print $2}')
export RUSTDOCFLAGS="--document-private-items --crate-version \"${STD_DATE}\" --html-in-header ${PWD}/in-head.html"
cargo doc --manifest-path library/std/Cargo.toml |
I can reproduce with that, thanks. I looked at the code that's failing and I'm surprised it worked with my |
Happy to fix that if hasn't been addressed yet. @rustbot claim |
I saw in rust-lang/rust#81037 that when you document private items with rustdoc the `x86 AVX-512 BITALG` feature comment does not contain scape characters in the message and therefore rustdoc was emiting warnings. This fixes it.
I saw in rust-lang/rust#81037 that when you document private items with rustdoc the `x86 AVX-512 BITALG` feature comment does not contain scape characters in the message and therefore rustdoc was emiting warnings. This fixes it.
…n514 Fix broken links with `--document-private-items` in the standard library As it was suggested in rust-lang#81037 `SpecFromIter` is not in the scope and therefore we get a warning when we try to do document private intems in `rust/library/alloc/`. This addresses rust-lang#81037 by adding the trait in the scope as `@jyn514` suggested and also adding an `allow(unused_imports)` flag so that the compiler does not complain, Since the trait is not used per se in the code, it's just needed to have properly documented docs.
…n514 Fix broken links with `--document-private-items` in the standard library As it was suggested in rust-lang#81037 `SpecFromIter` is not in the scope and therefore we get a warning when we try to do document private intems in `rust/library/alloc/`. This addresses rust-lang#81037 by adding the trait in the scope as ``@jyn514`` suggested and also adding an `allow(unused_imports)` flag so that the compiler does not complain, Since the trait is not used per se in the code, it's just needed to have properly documented docs.
…n514 Fix broken links with `--document-private-items` in the standard library As it was suggested in rust-lang#81037 `SpecFromIter` is not in the scope and therefore we get a warning when we try to do document private intems in `rust/library/alloc/`. This addresses rust-lang#81037 by adding the trait in the scope as ```@jyn514``` suggested and also adding an `allow(unused_imports)` flag so that the compiler does not complain, Since the trait is not used per se in the code, it's just needed to have properly documented docs.
rust/library/alloc/src/vec/spec_from_iter_nested.rs
Line 8 in dcf622e
And in stdarch submodule:
@rustbot label: T-rustdoc C-bug E-easy
The text was updated successfully, but these errors were encountered: