Repository navigation
rustdoc: private_doc_tests lint no longer fires on stable #75951
Description
Activity
- addedA-doctestsArea: Documentation tests, run by rustdocArea: Documentation tests, run by rustdocA-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.Area: Lints (warnings about flaws in source code) such as unused_mut.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.Relevant to the rustdoc team, which will review and decide on the PR/issue.
on Aug 26, 2020 - addedregression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.
on Aug 26, 2020 - addedI-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}Issue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
on Aug 26, 2020 This was definitely unintentional. I thought I added a test for this ...
Hmm, it tests with
deny(rustdoc)but not withdeny(missing_doc_code_examples). Maybe the name of the lint wasn't registered?https://github.com/rust-lang/rust/pull/74855/files#diff-2009d75a18198cb86d168844baa3c607
The issue is this line. Compiletest runs with RUSTC_BOOTSTRAP set. I don't recall off the top of my head how to force a test to be stable.
Wait now I'm confused. I thought the point of this lint was that it only runs on nightly, because we're not sure if we want to stabilize it.
cc @rust-lang/rustdoc
@ehuss are you sure this used to work?
The
private_doc_testslint has been on stable since 1.32. It is documented here.Got it, I mixed it up with
missing_doc_code_examples. Yeah this is a bug then - the two lints should be treated differently.- added a commit that references this issue
on Aug 26, 2020 Actually it looks like I introduced the opposite bug for
missing_doc_code_examples- it now runs on beta when it shouldn't.Assigning
P-highas discussed as part of the Prioritization Working Group procedure and removingI-prioritize.- addedP-highHigh priorityHigh priorityand removedI-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}Issue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
on Aug 26, 2020 - added a commit that references this issue
on Aug 28, 2020
As of
rustc 1.47.0-beta.1, theprivate_doc_testslint is no longer working.I expected to see this happen:
cargo docshould issuewarning: documentation test in private itemInstead, this happened: No warnings emitted.
This appears to have changed in #74855. I don't see any discussion there about this, so I'm guessing it was unintentional.
cc @jyn514.