rust/tests/ui/traits/object/with-self-in-projection-output-bad.rs
Esteban Küber 17a6ae2df3 Detect object safety errors when assoc type is missing
When an associated type with GATs isn't specified in a `dyn Trait`, emit
an object safety error instead of only complaining about the missing
associated type, as it will lead the user down a path of three different
errors before letting them know that what they were trying to do is
impossible to begin with.

Fix #103155.
2023-10-30 22:12:07 +00:00

51 lines
1.1 KiB
Rust

// Regression test for #56288. Checks that if a supertrait defines an associated type
// projection that references `Self`, then that associated type must still be explicitly
// specified in the `dyn Trait` variant, since we don't know what `Self` is anymore.
trait Base {
type Output;
}
trait Helper: Base<Output=<Self as Helper>::Target> {
type Target;
}
impl Base for u32
{
type Output = i32;
}
impl Helper for u32
{
type Target = i32;
}
trait ConstI32 {
type Out;
}
impl<T: ?Sized> ConstI32 for T {
type Out = i32;
}
// Test that you still need to manually give a projection type if the Output type
// is normalizable.
trait NormalizableHelper:
Base<Output=<Self as ConstI32>::Out>
{
type Target;
}
impl NormalizableHelper for u32
{
type Target = i32;
}
fn main() {
let _x: Box<dyn Helper<Target=i32>> = Box::new(2u32);
//~^ ERROR the value of the associated type `Output` in `Base` must be specified
let _y: Box<dyn NormalizableHelper<Target=i32>> = Box::new(2u32);
//~^ ERROR the value of the associated type `Output` in `Base` must be specified
}