Skip to content
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

Fix broken links with --document-private-items in the standard library #81179

Merged
merged 2 commits into from
Jan 21, 2021

Conversation

CPerezz
Copy link
Contributor

@CPerezz CPerezz commented Jan 18, 2021

As it was suggested in #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 #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.

As it was suggested in rust-lang#81037 `SpecFromIter` is not
in the scope and therefore (even it should fail),
we get a warning when we try do document private
intems in `rust/library/alloc/`.

This fixes rust-lang#81037 by adding the trait in the scope
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-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @cramertj (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jan 18, 2021
@jyn514 jyn514 added A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Jan 19, 2021
@jyn514 jyn514 changed the title Fix internal rustdoc broken links Fix broken links with --document-private-items in the standard library Jan 19, 2021
@jyn514
Copy link
Member

jyn514 commented Jan 19, 2021

@bors r+ rollup

I edited the description to remove 'fixes' because stdarch still gives warnings.

@bors
Copy link
Contributor

bors commented Jan 19, 2021

📌 Commit bc6720f has been approved by jyn514

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 19, 2021
@CPerezz
Copy link
Contributor Author

CPerezz commented Jan 20, 2021

@bors r+ rollup

I edited the description to remove 'fixes' because stdarch still gives warnings.

I already made a PR to stdarch and got merged to solve them. So should be cleared in the next release.

m-ou-se added a commit to m-ou-se/rust that referenced this pull request Jan 20, 2021
…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.
m-ou-se added a commit to m-ou-se/rust that referenced this pull request Jan 20, 2021
…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.
bors added a commit to rust-lang-ci/rust that referenced this pull request Jan 21, 2021
Rollup of 11 pull requests

Successful merges:

 - rust-lang#79655 (Add Vec visualization to understand capacity)
 - rust-lang#80172 (Use consistent punctuation for 'Prelude contents' docs)
 - rust-lang#80429 (Add regression test for mutual recursion in obligation forest)
 - rust-lang#80601 (Improve grammar in documentation of format strings)
 - rust-lang#81046 (Improve unknown external crate error)
 - rust-lang#81178 (Visit only terminators when removing landing pads)
 - rust-lang#81179 (Fix broken links with `--document-private-items` in the standard library)
 - rust-lang#81184 (Remove unnecessary `after_run` function)
 - rust-lang#81185 (Fix ICE in mir when evaluating SizeOf on unsized type)
 - rust-lang#81187 (Fix typo in counters.rs)
 - rust-lang#81219 (Document security implications of std::env::temp_dir)

Failed merges:

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit b76f0f9 into rust-lang:master Jan 21, 2021
@rustbot rustbot added this to the 1.51.0 milestone Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants