Auto merge of #67940 - JohnTitor:rustc-guide, r=JohnTitor

[rust.git] / src / librustc_lint / passes.rs

diff --git a/src/librustc_lint/passes.rs b/src/librustc_lint/passes.rs
index cb54105381fb2f37d75ffbca59f98b70bbe15fff..7e5d670767ad80de22d057a4efa63ba194456a2d 100644 (file)
--- a/src/librustc_lint/passes.rs
+++ b/src/librustc_lint/passes.rs
@@ -1,23 +1,3 @@
-//! Lints, aka compiler warnings.
-//!
-//! A 'lint' check is a kind of miscellaneous constraint that a user _might_
-//! want to enforce, but might reasonably want to permit as well, on a
-//! module-by-module basis. They contrast with static constraints enforced by
-//! other phases of the compiler, which are generally required to hold in order
-//! to compile the program at all.
-//!
-//! Most lints can be written as `LintPass` instances. These run after
-//! all other analyses. The `LintPass`es built into rustc are defined
-//! within `builtin.rs`, which has further comments on how to add such a lint.
-//! rustc can also load user-defined lint plugins via the plugin mechanism.
-//!
-//! Some of rustc's lints are defined elsewhere in the compiler and work by
-//! calling `add_lint()` on the overall `Session` object. This works when
-//! it happens before the main lint pass, which emits the lints stored by
-//! `add_lint()`. To emit lints after the main lint pass (from codegen, for
-//! example) requires more effort. See `emit_lint` and `GatherNodeLevels`
-//! in `context.rs`.
-
 use crate::context::{EarlyContext, LateContext};
 
 use rustc_data_structures::sync;