Skip to content

Conversation

@flodiebold
Copy link
Member

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.

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.
@flodiebold flodiebold requested a review from matklad February 29, 2020 14:36
@matklad
Copy link
Contributor

matklad commented Feb 29, 2020

bors r+

@bors
Copy link
Contributor

bors bot commented Feb 29, 2020

@bors bors bot merged commit 0ae7054 into rust-lang:master Feb 29, 2020
@flodiebold flodiebold deleted the rvalue-hint branch February 29, 2020 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants