mirror of
https://github.com/rust-lang/rust.git
synced 2025-10-31 13:04:42 +00:00
fbd548acc3
Including unstable lints in the lint group produces unintuitive behavior on stable (see #106289). Meanwhile, if we only included unstable lints on nightly and not on stable, we could end up with confusing bugs that were hard to compare across versions of Rust that lacked code changes. I think that only including stable lints in `rustdoc::all`, no matter the release channel, is the most intuitive option. Users can then control unstable lints individually, which is reasonable since they have to enable the feature gates individually anyway.
33 lines
727 B
Rust
33 lines
727 B
Rust
#![feature(rustdoc_missing_doc_code_examples)]
|
|
|
|
//! Documenting the kinds of lints emitted by rustdoc.
|
|
//!
|
|
//! ```
|
|
//! println!("sup");
|
|
//! ```
|
|
|
|
#![deny(rustdoc::missing_doc_code_examples)]
|
|
#![deny(rustdoc::all)]
|
|
|
|
/// what up, let's make an [error]
|
|
///
|
|
/// ```
|
|
/// println!("sup");
|
|
/// ```
|
|
pub fn link_error() {} //~^^^^^ ERROR unresolved link to `error`
|
|
|
|
/// wait, this doesn't have a doctest?
|
|
pub fn no_doctest() {} //~^ ERROR missing code example in this documentation
|
|
|
|
/// wait, this *does* have a doctest?
|
|
///
|
|
/// ```
|
|
/// println!("sup");
|
|
/// ```
|
|
fn private_doctest() {} //~^^^^^ ERROR documentation test in private item
|
|
|
|
/// <unknown>
|
|
//~^ ERROR unclosed HTML tag `unknown`
|
|
//~^^ ERROR missing code example
|
|
pub fn c() {}
|