Module foreign_modules 

Re-exports

use rustc_abi::FIRST_VARIANT; 🔒

use rustc_attr_ir::find_attr; 🔒

use rustc_data_structures::unord::UnordMap; 🔒

use rustc_data_structures::unord::UnordSet; 🔒

use rustc_hir as hir; 🔒

use rustc_hir::def::DefKind; 🔒

use rustc_lint_defs::declare_lint; 🔒

use rustc_middle::query::Providers; 🔒

use rustc_middle::ty; 🔒

use rustc_middle::ty::AdtDef; 🔒

use rustc_middle::ty::Instance; 🔒

use rustc_middle::ty::Ty; 🔒

use rustc_middle::ty::TyCtxt; 🔒

use rustc_span::Span; 🔒

use rustc_span::Symbol; 🔒

use tracing::debug; 🔒

use tracing::instrument; 🔒

use tracing::instrument; 🔒

use crate::diagnostics::BuiltinClashingExtern; 🔒

use crate::diagnostics::BuiltinClashingExternSub; 🔒

use crate::LintVec; 🔒

use crate::types; 🔒

Structs

ClashingExternDeclarations 🔒

Enums

SymbolName 🔒

Differentiate between whether the name for an extern decl came from the link_name attribute or just from declaration itself. This is important because we don’t want to report clashes on symbol name if they don’t actually clash because one or the other links against a symbol with a different name.

Statics

CLASHING_EXTERN_DECLARATIONS

The clashing_extern_declarations lint detects when an extern fn has been declared with the same name but different types.

Functions

clashing_extern_declarations 🔒

get_relevant_span 🔒

We want to ensure that we use spans for both decls that include where the name was defined, whether that was from the link_name attribute or not.

lint_vec 🔒

name_of_extern_decl 🔒

Get the name of the symbol that’s linked against for a given extern declaration. That is, the name specified in a #[link_name = …] attribute if one was specified, else, just the symbol’s name.

provide 🔒

structurally_same_type 🔒

Checks whether two types are structurally the same enough that the declarations shouldn’t clash. We need this so we don’t emit a lint when two modules both declare an extern struct, with the same members (as the declarations shouldn’t clash).

structurally_same_type_impl 🔒