5fe220b987
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.
|
||
|---|---|---|
| .. | ||
| coerce.rs | ||
| expr.rs | ||
| pat.rs | ||
| path.rs | ||
| unify.rs | ||