rust/tests/ui/issues/issue-25679.rs

//@ run-pass
trait Device {
    type Resources;
}
#[allow(dead_code)]
struct Foo<D, R>(D, R);

impl<D: Device> Foo<D, D::Resources> {
    fn present(&self) {}
}

struct Res;
struct Dev;

impl Device for Dev { type Resources = Res; }

fn main() {
    let foo = Foo(Dev, Res);
    foo.present();
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
Don't call instantiate_type_scheme during method probing It can introduce obligations to the fulfillment context, which would incorrectly still remain after the probe finished. Fixes #25679. 2015-06-13 23:34:03 +03:00			`trait Device {`
			`type Resources;`
			`}`
Adjust compiler tests for unused_tuple_struct_fields -> dead_code 2023-12-27 17:11:58 -05:00			`#[allow(dead_code)]`
Don't call instantiate_type_scheme during method probing It can introduce obligations to the fulfillment context, which would incorrectly still remain after the probe finished. Fixes #25679. 2015-06-13 23:34:03 +03:00			`struct Foo<D, R>(D, R);`

Make impl-trait-ref associated types work in methods 2015-06-14 02:27:18 +03:00			`impl<D: Device> Foo<D, D::Resources> {`
Don't call instantiate_type_scheme during method probing It can introduce obligations to the fulfillment context, which would incorrectly still remain after the probe finished. Fixes #25679. 2015-06-13 23:34:03 +03:00			`fn present(&self) {}`
			`}`

			`struct Res;`
			`struct Dev;`

			`impl Device for Dev { type Resources = Res; }`

			`fn main() {`
			`let foo = Foo(Dev, Res);`
			`foo.present();`
			`}`