Struct rustc_mir::borrow_check::region_infer::TypeTest [−][src]
pub struct TypeTest<'tcx> {
pub generic_kind: GenericKind<'tcx>,
pub lower_bound: RegionVid,
pub locations: Locations,
pub verify_bound: VerifyBound<'tcx>,
}Expand description
A “type test” corresponds to an outlives constraint between a type
and a lifetime, like T: 'x or <T as Foo>::Bar: 'x. They are
translated from the Verify region constraints in the ordinary
inference context.
These sorts of constraints are handled differently than ordinary
constraints, at least at present. During type checking, the
InferCtxt::process_registered_region_obligations method will
attempt to convert a type test like T: 'x into an ordinary
outlives constraint when possible (for example, &'a T: 'b will
be converted into 'a: 'b and registered as a Constraint).
In some cases, however, there are outlives relationships that are not converted into a region constraint, but rather into one of these “type tests”. The distinction is that a type test does not influence the inference result, but instead just examines the values that we ultimately inferred for each region variable and checks that they meet certain extra criteria. If not, an error can be issued.
One reason for this is that these type tests typically boil down
to a check like 'a: 'x where 'a is a universally quantified
region – and therefore not one whose value is really meant to be
inferred, precisely (this is not always the case: one can have a
type test like <Foo as Trait<'?0>>::Bar: 'x, where '?0 is an
inference variable). Another reason is that these type tests can
involve disjunction – that is, they can be satisfied in more
than one way.
For more information about this translation, see
InferCtxt::process_registered_region_obligations and
InferCtxt::type_must_outlive in rustc_infer::infer::InferCtxt.
Fields
generic_kind: GenericKind<'tcx>Expand description
The type T that must outlive the region.
lower_bound: RegionVidExpand description
The region 'x that the type must outlive.
locations: LocationsExpand description
Where did this constraint arise and why?
verify_bound: VerifyBound<'tcx>Expand description
A test which, if met by the region 'x, proves that this type
constraint is satisfied.
Trait Implementations
Auto Trait Implementations
impl<'tcx> !RefUnwindSafe for TypeTest<'tcx>
impl<'tcx> !Send for TypeTest<'tcx>
impl<'tcx> !Sync for TypeTest<'tcx>
impl<'tcx> Unpin for TypeTest<'tcx>
impl<'tcx> !UnwindSafe for TypeTest<'tcx>
Blanket Implementations
impl<T> BorrowMut<T> for T where
T: ?Sized, [src]
impl<T> BorrowMut<T> for T where
T: ?Sized, [src]pub fn borrow_mut(&mut self) -> &mut T[src]
pub fn borrow_mut(&mut self) -> &mut T[src]Mutably borrows from an owned value. Read more
impl<T> ToOwned for T where
T: Clone, [src]
impl<T> ToOwned for T where
T: Clone, [src]type Owned = T
type Owned = TThe resulting type after obtaining ownership.
pub fn to_owned(&self) -> T[src]
pub fn to_owned(&self) -> T[src]Creates owned data from borrowed data, usually by cloning. Read more
pub fn clone_into(&self, target: &mut T)[src]
pub fn clone_into(&self, target: &mut T)[src]🔬 This is a nightly-only experimental API. (toowned_clone_into)
recently added
Uses borrowed data to replace owned data, usually by cloning. Read more
impl<T> WithConstness for T[src]
impl<T> WithConstness for T[src]