1
Fork 0

Use != Positive rather than == Negative

Feels more complete, and for ImplPolarity has the side-effect of making
sure we also handle reservation impls correctly
This commit is contained in:
Michael Goulet 2024-03-21 15:46:40 -04:00
parent 4b87c0b9c9
commit 127e42d33b
6 changed files with 6 additions and 6 deletions

View file

@ -270,7 +270,7 @@ impl<'tcx, O: Elaboratable<'tcx>> Elaborator<'tcx, O> {
match bound_clause.skip_binder() {
ty::ClauseKind::Trait(data) => {
// Negative trait bounds do not imply any supertrait bounds
if data.polarity == ty::PredicatePolarity::Negative {
if data.polarity != ty::PredicatePolarity::Positive {
return;
}
// Get predicates implied by the trait, or only super predicates if we only care about self predicates.