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

Fixed naive doc formatting for #[must_use] lints #7827

Merged
merged 1 commit into from
Oct 16, 2021

Conversation

zvavybir
Copy link
Contributor

The documentation of a few lints around the #[must_use] attribute had a few times "[#[must_use]]" (without the parentheses, but with the []) and once the "`" was missing.

changelog: Fixed naive doc formatting for #[must_use] lints ([must_use_unit], [double_must_use], [must_use_candidate], [let_underscore_must_use])

@rust-highfive
Copy link

r? @xFrednet

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties label Oct 16, 2021
///
/// ### Why is this bad?
/// It's better to explicitly
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, most of these doc comments intentionally use an extra link for must_use. These comments are exported and rendered on Clippy's lint list which doesn't automatically lint to Rust's attributes and symbols. Therefore, it wouldn't be good to change it in the lint documentation.

This adjustment is correct, though. Could you revert, the other changes and add a link for the attributes in this lint documentation? 🙃

Copy link
Contributor Author

@zvavybir zvavybir Oct 16, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, but I don't quite understand you. For me this website looks so (screenshot from the must_use_candidate lint):
Screenshot_20211016_175219
Is this here shown behaviour really the desired one? I started this PR to get the outer [] away and when I looked more closely I saw that this "link" doesn't actual work, so I removed it too. Was this wrong?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, I believe that GH actually accepts code like that. Let's see [#[must_use]]

[#[must_use]]: https://doc.rust-lang.org/reference/attributes/diagnostics.html#the-must_use-attribute


Apparently not, TIL. I thought that markdown would accept that, but apparently it doesn't. This makes a lot more sense now. Thank you for checking 🙃

@xFrednet
Copy link
Member

Thank you for the update 👍

@bors r+

@bors
Copy link
Contributor

bors commented Oct 16, 2021

📌 Commit 25ff7ce has been approved by xFrednet

@bors
Copy link
Contributor

bors commented Oct 16, 2021

⌛ Testing commit 25ff7ce with merge d50cfd2...

@bors
Copy link
Contributor

bors commented Oct 16, 2021

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: xFrednet
Pushing d50cfd2 to master...

@bors bors merged commit d50cfd2 into rust-lang:master Oct 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants