Module rustc_lint::internal

Some lints that are only useful in the compiler or crates that use compiler internals, such as Clippy.

Structs

• BadOptAccess
• DefaultHashTypes
• Diagnostics
• ExistingDocKeyword
• LintPassImpl
• QueryStability
• SpanUseEqCtxt
• TyTyKind

Statics

• BAD_OPT_ACCESS
  The bad_opt_access lint detects accessing options by field instead of the wrapper function.
• DEFAULT_HASH_TYPES
  The default_hash_type lint detects use of std::collections::HashMap/std::collections::HashSet, suggesting the use of FxHashMap/FxHashSet.
• DIAGNOSTIC_OUTSIDE_OF_IMPL
  The diagnostic_outside_of_impl lint detects calls to functions annotated with #[rustc_lint_diagnostics] that are outside an Diagnostic, Subdiagnostic, or LintDiagnostic impl (either hand-written or derived).
• EXISTING_DOC_KEYWORD
  The existing_doc_keyword lint detects use #[doc()] keywords that don’t exist, e.g. #[doc(keyword = "..")].
• LINT_PASS_IMPL_WITHOUT_MACRO
  The lint_pass_impl_without_macro detects manual implementations of a lint pass, without using declare_lint_pass or impl_lint_pass.
• POTENTIAL_QUERY_INSTABILITY
  The potential_query_instability lint detects use of methods which can lead to potential query instability, such as iterating over a HashMap.
• SPAN_USE_EQ_CTXT
• UNTRANSLATABLE_DIAGNOSTIC
  The untranslatable_diagnostic lint detects messages passed to functions with impl Into<{D,Subd}iagMessage parameters without using translatable Fluent strings.
• USAGE_OF_QUALIFIED_TY
  The usage_of_qualified_ty lint detects usages of ty::TyKind, where Ty should be used instead.
• USAGE_OF_TY_TYKIND
  The usage_of_ty_tykind lint detects usages of ty::TyKind::<kind>, where ty::<kind> would suffice.

Functions

• gen_args 🔒
• is_doc_keyword 🔒
• is_span_ctxt_call 🔒
• is_ty_or_ty_ctxt 🔒
• lint_ty_kind_usage 🔒
• typeck_results_of_method_fn 🔒
  Helper function for lints that check for expressions with calls and use typeck results to get the DefId and GenericArgsRef of the function.