Module generics

Re-exports§

use std::assert_matches; 🔒
use hir::HirId; 🔒
use hir::def::DefKind; 🔒
use hir::def::Res; 🔒
use rustc_data_structures::fx::FxHashSet; 🔒
use rustc_hir as hir; 🔒
use rustc_hir::def_id::DefId; 🔒
use rustc_middle::ty; 🔒
use rustc_middle::ty::GenericParamDefKind; 🔒
use rustc_middle::ty::TyCtxt; 🔒
use rustc_span::symbol::kw; 🔒
use rustc_span::ErrorGuaranteed; 🔒
use rustc_span::Ident; 🔒
use rustc_span::Span; 🔒
use rustc_span::bug; 🔒
use rustc_span::sym; 🔒
use crate::LoweringContext; 🔒
use crate::delegation::resolution::resolver::DelegationResolver; 🔒
use crate::diagnostics::DelegationInfersMismatch; 🔒
use crate::diagnostics::DelegationToInherentImplMustContainParentGenerics; 🔒
use crate::diagnostics::DelegationToInherentImplParentContainsInfer; 🔒
use rustc_ast::*; 🔒

GenericArgSlot 🔒
GenericsPosition 🔒
HirOrTyGenerics 🔒: Used for storing either ty generics or their uplifted HIR version. First we obtain ty generics. Next, at some point of generics processing we need to uplift those generics to HIR, for this purpose we use into_hir_generics that uplifts ty generics and replaces Ty variant with Hir. Such approach is useful as we can call this method at any time knowing that uplifting will occur at most only once. Then, in order to obtain generic params or args we use hir_generics_or_empty or into_generic_args functions. There also may be situations when we obtained ty generics but never uplifted them to HIR, meaning we did not propagate them and thus we do not need to generate generic params (i.e., method call scenarios), in such a case this approach helps a lot as if into_hir_generics will not be called then uplifting will not happen.
ParentSegmentArgs 🔒