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.

0 files changed, 0 insertions, 0 deletions