3ae974f025
This solves the method call part of issue https://github.com/rust-lang/rust/issues/69455 I added a `target_span` field so as to pin down the exact location of the error. We need a dedicated field `found_exact_method_call` to prioritize situations like the test case `issue-69455.rs`. If we reuse `found_method_call`, `found_local_pattern` will show up first. We can not move `found_method_call` up, it is undesirable in various situations.
31 lines
657 B
Rust
31 lines
657 B
Rust
// Regression test for #69455: projection predicate was not satisfied.
|
|
// Compiler should indicate the correct location of the
|
|
// unsatisfied projection predicate
|
|
|
|
pub trait Test<Rhs = Self> {
|
|
type Output;
|
|
|
|
fn test(self, rhs: Rhs) -> Self::Output;
|
|
}
|
|
|
|
impl Test<u32> for u64 {
|
|
type Output = u64;
|
|
|
|
fn test(self, other: u32) -> u64 {
|
|
self + (other as u64)
|
|
}
|
|
}
|
|
|
|
impl Test<u64> for u64 {
|
|
type Output = u64;
|
|
|
|
fn test(self, other: u64) -> u64 {
|
|
(self + other) as u64
|
|
}
|
|
}
|
|
|
|
fn main() {
|
|
let xs: Vec<u64> = vec![1, 2, 3];
|
|
println!("{}", 23u64.test(xs.iter().sum())); //~ ERROR: type annotations needed [E0284]
|
|
}
|