Florian Diebold 5fe220b987 Fix a common false-positive type mismatch
E.g. for `&{ some_string() }` in a context where a `&str` is expected, we
reported a mismatch inside the block. The problem is that we're passing an
expectation of `str` down, but the expectation is more of a hint in this case.
There's a long comment in rustc about this, which I just copied.

Also, fix reported location for type mismatches in macros.
2020-02-29 15:31:07 +01:00
..
2019-12-20 15:14:30 -05:00
2020-02-07 18:28:10 +01:00
2020-02-18 16:12:37 +02:00
2020-02-14 15:01:42 +01:00
2020-02-19 18:17:09 +01:00
2020-02-14 20:32:55 +00:00
2020-02-18 16:12:37 +02:00
2020-02-18 16:12:37 +02:00
2020-02-27 16:16:13 +01:00