Struct rustc_trait_selection::traits::query::type_op::outlives::DropckOutlives
source · [−]pub struct DropckOutlives<'tcx> {
dropped_ty: Ty<'tcx>,
}Fields
dropped_ty: Ty<'tcx>Implementations
Trait Implementations
type Lifted = DropckOutlives<'__lifted>
type QueryResponse = DropckOutlivesResult<'tcx>
fn try_fast_path(
tcx: TyCtxt<'tcx>,
key: &ParamEnvAnd<'tcx, Self>
) -> Option<Self::QueryResponse>
fn try_fast_path(
tcx: TyCtxt<'tcx>,
key: &ParamEnvAnd<'tcx, Self>
) -> Option<Self::QueryResponse>
Give query the option for a simple fast path that never
actually hits the tcx cache lookup etc. Return Some(r) with
a final result or None to do the full path. Read more
fn perform_query(
tcx: TyCtxt<'tcx>,
canonicalized: Canonicalized<'tcx, ParamEnvAnd<'tcx, Self>>
) -> Fallible<CanonicalizedQueryResponse<'tcx, Self::QueryResponse>>
fn perform_query(
tcx: TyCtxt<'tcx>,
canonicalized: Canonicalized<'tcx, ParamEnvAnd<'tcx, Self>>
) -> Fallible<CanonicalizedQueryResponse<'tcx, Self::QueryResponse>>
Performs the actual query with the canonicalized key – the
real work happens here. This method is not given an infcx
because it shouldn’t need one – and if it had access to one,
it might do things like invoke sub_regions, which would be
bad, because it would create subregion relationships that are
not captured in the return value. Read more
fn fully_perform_into(
query_key: ParamEnvAnd<'tcx, Self>,
infcx: &InferCtxt<'_, 'tcx>,
output_query_region_constraints: &mut QueryRegionConstraints<'tcx>
) -> Fallible<(Self::QueryResponse, Option<Canonical<'tcx, ParamEnvAnd<'tcx, Self>>>, PredicateObligations<'tcx>, Certainty)>
fn try_super_fold_with<__F: FallibleTypeFolder<'tcx>>(
self,
__folder: &mut __F
) -> Result<Self, __F::Error>
fn super_visit_with<__F: TypeVisitor<'tcx>>(
&self,
__folder: &mut __F
) -> ControlFlow<__F::BreakTy>
Consumers may find this more convenient to use with infallible folders than
try_super_fold_with, to which the
provided default definition delegates. Implementors should not override
this provided default definition, to ensure that the two methods are coherent
(provide a definition of try_super_fold_with instead). Read more
Consumers may find this more convenient to use with infallible folders than
try_fold_with, to which the provided
default definition delegates. Implementors should not override this
provided default definition, to ensure that the two methods are coherent
(provide a definition of try_fold_with instead). Read more
fn try_fold_with<F>(
self,
folder: &mut F
) -> Result<Self, <F as TypeFolder<'tcx>>::Error> where
F: FallibleTypeFolder<'tcx>,
fn visit_with<V>(
&self,
visitor: &mut V
) -> ControlFlow<<V as TypeVisitor<'tcx>>::BreakTy, ()> where
V: TypeVisitor<'tcx>,
Returns true if self has any late-bound regions that are either
bound by binder or bound by some binder outside of binder.
If binder is ty::INNERMOST, this indicates whether
there are any late-bound regions that appear free. Read more
Returns true if this self has any regions that escape binder (and
hence are not bound by it). Read more
“Free” regions in this context means that it has any region that is not (a) erased or (b) late-bound. Read more
True if there are any un-erased free regions.
Indicates whether this value references only ‘global’ generic parameters that are the same regardless of what fn we are in. This is used for caching. Read more
True if there are any late-bound regions
Indicates whether this value still has parameters/placeholders/inference variables
which could be replaced later, in a way that would change the results of impl
specialization. Read more
Auto Trait Implementations
impl<'tcx> !RefUnwindSafe for DropckOutlives
impl<'tcx> Send for DropckOutlives
impl<'tcx> Sync for DropckOutlives
impl<'tcx> Unpin for DropckOutlives
impl<'tcx> !UnwindSafe for DropckOutlives
Blanket Implementations
Mutably borrows from an owned value. Read more
Layout
Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference’s “Type Layout” chapter for details on type layout guarantees.
Size: 8 bytes