@@ -608,13 +608,13 @@ declare_lint! {
608608}
609609
610610declare_lint ! {
611- /// The `unfulfilled_lint_expectations` lint detects lint trigger expectations
612- /// that have not been fulfilled .
611+ /// The `unfulfilled_lint_expectations` lint warns if a lint expectation is
612+ /// unfulfilled .
613613 ///
614614 /// ### Example
615615 ///
616616 /// ```rust
617- /// #![feature(lint_reasons)]
617+ /// #![cfg_attr(bootstrap, feature(lint_reasons) )]
618618 ///
619619 /// #[expect(unused_variables)]
620620 /// let x = 10;
@@ -625,24 +625,14 @@ declare_lint! {
625625 ///
626626 /// ### Explanation
627627 ///
628- /// It was expected that the marked code would emit a lint. This expectation
629- /// has not been fulfilled.
628+ /// The `#[expect]` attribute can be used to create a lint expectation. The
629+ /// expectation is fulfilled, if a `#[warn]` attribute at the same location
630+ /// would result in a lint emission. If the expectation is unfulfilled,
631+ /// because no lint was emitted, this lint will be emitted on the attribute.
630632 ///
631- /// The `expect` attribute can be removed if this is intended behavior otherwise
632- /// it should be investigated why the expected lint is no longer issued.
633- ///
634- /// In rare cases, the expectation might be emitted at a different location than
635- /// shown in the shown code snippet. In most cases, the `#[expect]` attribute
636- /// works when added to the outer scope. A few lints can only be expected
637- /// on a crate level.
638- ///
639- /// Part of RFC 2383. The progress is being tracked in [#54503]
640- ///
641- /// [#54503]: https://github.com/rust-lang/rust/issues/54503
642633 pub UNFULFILLED_LINT_EXPECTATIONS ,
643634 Warn ,
644- "unfulfilled lint expectation" ,
645- @feature_gate = rustc_span:: sym:: lint_reasons;
635+ "unfulfilled lint expectation"
646636}
647637
648638declare_lint ! {
0 commit comments