1
Fork 0

Properly consider binder vars in HasTypeFlagsVisitor

This commit is contained in:
Michael Goulet 2023-09-14 03:49:41 +00:00
parent 5adddad28c
commit 7ae301ec47
3 changed files with 72 additions and 15 deletions

View file

@ -34,6 +34,26 @@ impl FlagComputation {
result.flags result.flags
} }
pub fn bound_var_flags(vars: &ty::List<ty::BoundVariableKind>) -> FlagComputation {
let mut computation = FlagComputation::new();
for bv in vars {
match bv {
ty::BoundVariableKind::Ty(_) => {
computation.flags |= TypeFlags::HAS_TY_LATE_BOUND;
}
ty::BoundVariableKind::Region(_) => {
computation.flags |= TypeFlags::HAS_RE_LATE_BOUND;
}
ty::BoundVariableKind::Const => {
computation.flags |= TypeFlags::HAS_CT_LATE_BOUND;
}
}
}
computation
}
fn add_flags(&mut self, flags: TypeFlags) { fn add_flags(&mut self, flags: TypeFlags) {
self.flags = self.flags | flags; self.flags = self.flags | flags;
} }
@ -57,21 +77,7 @@ impl FlagComputation {
where where
F: FnOnce(&mut Self, T), F: FnOnce(&mut Self, T),
{ {
let mut computation = FlagComputation::new(); let mut computation = FlagComputation::bound_var_flags(value.bound_vars());
for bv in value.bound_vars() {
match bv {
ty::BoundVariableKind::Ty(_) => {
computation.flags |= TypeFlags::HAS_TY_LATE_BOUND;
}
ty::BoundVariableKind::Region(_) => {
computation.flags |= TypeFlags::HAS_RE_LATE_BOUND;
}
ty::BoundVariableKind::Const => {
computation.flags |= TypeFlags::HAS_CT_LATE_BOUND;
}
}
}
f(&mut computation, value.skip_binder()); f(&mut computation, value.skip_binder());

View file

@ -481,9 +481,33 @@ impl std::fmt::Debug for HasTypeFlagsVisitor {
// `Ty`/`Const`/`Predicate`, but not within those types. This is because the // `Ty`/`Const`/`Predicate`, but not within those types. This is because the
// type flags at the outer layer are enough. So it's faster than it first // type flags at the outer layer are enough. So it's faster than it first
// looks, particular for `Ty`/`Predicate` where it's just a field access. // looks, particular for `Ty`/`Predicate` where it's just a field access.
//
// N.B. The only case where this isn't totally true is binders, which also
// add `HAS_{RE,TY,CT}_LATE_BOUND` flag depending on the *bound variables* that
// are present, regardless of whether those bound variables are used. This
// is important for anonymization of binders in `TyCtxt::erase_regions`. We
// specifically detect this case in `visit_binder`.
impl<'tcx> TypeVisitor<TyCtxt<'tcx>> for HasTypeFlagsVisitor { impl<'tcx> TypeVisitor<TyCtxt<'tcx>> for HasTypeFlagsVisitor {
type BreakTy = FoundFlags; type BreakTy = FoundFlags;
fn visit_binder<T: TypeVisitable<TyCtxt<'tcx>>>(
&mut self,
t: &Binder<'tcx, T>,
) -> ControlFlow<Self::BreakTy> {
// If we're looking for any of the HAS_*_LATE_BOUND flags, we need to
// additionally consider the bound vars on the binder itself, even if
// the contents of a the binder (e.g. a `TraitRef`) doesn't reference
// the bound vars.
if self.flags.intersects(TypeFlags::HAS_LATE_BOUND) {
let bound_var_flags = FlagComputation::bound_var_flags(t.bound_vars());
if bound_var_flags.flags.intersects(self.flags) {
return ControlFlow::Break(FoundFlags);
}
}
t.super_visit_with(self)
}
#[inline] #[inline]
fn visit_ty(&mut self, t: Ty<'tcx>) -> ControlFlow<Self::BreakTy> { fn visit_ty(&mut self, t: Ty<'tcx>) -> ControlFlow<Self::BreakTy> {
// Note: no `super_visit_with` call. // Note: no `super_visit_with` call.

View file

@ -0,0 +1,27 @@
// build-pass
// issue: #115807
trait Chip: for<'a> TraitWithLifetime<'a> + SomeMarker {
fn compute(&self);
}
trait SomeMarker {}
trait TraitWithLifetime<'a>: SomeMarker {}
trait Machine {
fn run();
}
struct BasicMachine;
impl Machine for BasicMachine {
fn run() {
let chips: [&dyn Chip; 0] = [];
let _ = chips.map(|chip| chip.compute());
}
}
fn main() {
BasicMachine::run();
}