Repository navigation
inherent method selection uses subtyping even when using paths #126227
Description
struct B<T>(T);
impl B<fn(&'static ())> {
fn method(self) {
println!("hey");
}
}
fn foo(x: B<for<'a> fn(&'a ())>) {
x.method(); // ok, method call
B::<for<'a> fn(&'a ())>::method(x); // ok, explicit path
}
fn main() {
}I would like us to change method selection for associated items to use equality. It feels very wrong to completely ignore the user type annotation here:
struct B<T>(T);
impl B<fn(&'static ())> {
fn method(self) {
println!("hey");
}
}
fn foo(y: B<fn(&'static ())>) {
// looks like it requires a hr fn pointer,
// but we never check that.
B::<for<'a> fn(&'a ())>::method(y);
}
fn main() {}Reacted by Michael Goulet and Boxy
Activity
Auto merge of rust-lang#129073 - compiler-errors:receiver-variance, r…
Rollup merge of rust-lang#129073 - compiler-errors:receiver-variance,…
Auto merge of rust-lang#129073 - compiler-errors:receiver-variance, r…