Skip to content

Inlined inherent methods are duplicated in documentation #14584

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

Closed
alexcrichton opened this issue Jun 1, 2014 · 1 comment
Closed

Inlined inherent methods are duplicated in documentation #14584

alexcrichton opened this issue Jun 1, 2014 · 1 comment
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@alexcrichton
Copy link
Member

For example, http://doc.rust-lang.org/sync/struct.Weak.html

@alexcrichton
Copy link
Member Author

Implementors are also duplicated: http://doc.rust-lang.org/std/str/trait.CharEq.html

alexcrichton added a commit to alexcrichton/rust that referenced this issue Jun 2, 2014
Inlining caused implementors to show up multiple times.

cc rust-lang#14584
mcpherrinm pushed a commit to mcpherrinm/rust that referenced this issue Jun 10, 2014
If the type associated with the impl is `pub use`'d or referenced twice in a
downstream crate, the impl will attempt to be inlined twice.

Closes rust-lang#14584
mcpherrinm pushed a commit to mcpherrinm/rust that referenced this issue Jun 10, 2014
Inlining caused implementors to show up multiple times.

cc rust-lang#14584
bors added a commit to rust-lang-ci/rust that referenced this issue Jun 5, 2023
internal: Report item-level macro expansion syntax errors
bors pushed a commit to rust-lang-ci/rust that referenced this issue Apr 22, 2025
… the following item is nameless (rust-lang#14584)

Fixes rust-lang/rust-clippy#14515.

changelog: [`empty_line_after_doc_comments`]: Fix a help message for
cases where the following item is nameless.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

1 participant