granite-rust/src/test/ui/issues/issue-69455.stderr

error[E0284]: type annotations needed: cannot satisfy `<u64 as Test<_>>::Output == _`
  --> $DIR/issue-69455.rs:29:26
   |
LL |     println!("{}", 23u64.test(xs.iter().sum()));
   |                          ^^^^ cannot satisfy `<u64 as Test<_>>::Output == _`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0284`.
Fix E0284 to not use incorrect wording Fix #71584, fix #69683. 2020-05-06 15:26:03 -07:00			error[E0284]: type annotations needed: cannot satisfy `<u64 as Test<_>>::Output == _`
fix misleading type annotation diagonstics 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. 2020-02-25 18:15:23 +08:00			`--> $DIR/issue-69455.rs:29:26`
			`\|`
			`LL \| println!("{}", 23u64.test(xs.iter().sum()));`
Fix E0284 to not use incorrect wording Fix #71584, fix #69683. 2020-05-06 15:26:03 -07:00			\| ^^^^ cannot satisfy `<u64 as Test<_>>::Output == _`
fix misleading type annotation diagonstics 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. 2020-02-25 18:15:23 +08:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0284`.