This can never happen currently because we always hit ambiguity when normalizing a TAIT during candidate assembly. We probably should protect against it regardless, but I don't think we have any tests that are unsound currently.

I couldn't think of a more creative test than this tho:

#![feature(type_alias_impl_trait)]

mod foo {
    type Tait = impl Sized;

    pub struct Wrapper(Tait);

    fn test() -> Tait { std::ptr::null_mut::<()>() }
}

trait Foo {}

impl<T: Send> Foo for T {}

impl Foo for foo::Wrapper {}
//~^ ERROR conflict implementations of trait `Foo` for type `Wrapper`

opaque auto trait leakage in coherence#65

Description

lcnropenedon Oct 2, 2023

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

opaque auto trait leakage in coherence
#65

lcnr
openedon Oct 2, 2023