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

// run-pass
trait Device {
    type Resources;
}
#[allow(unused_tuple_struct_fields)]
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();
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02: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;`
			`}`
Warn about dead tuple struct fields 2022-07-25 22:36:03 +02:00			`#[allow(unused_tuple_struct_fields)]`
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();`
			`}`