Uh oh!
There was an error while loading. Please reload this page.
Don't stop evaluating due to errors before borrow checking - #60125
Conversation
This comment has been minimized.
This comment has been minimized.
c3725fe to
595a151CompareUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
this span isn't quite right. I think it should point to op_string
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
this diagnostic is actually better than the first one.
This comment has been minimized.
This comment has been minimized.
595a151 to
87ef96dCompareestebank
commented
Apr 22, 2019
@oli-obk It seems to me that with the change made in this PR, we can safely disable everything in |
| Enum::A(_) if { x = Enum::B(false); false } => 1, | ||
| //~^ ERROR cannot assign in a pattern guard | ||
| //~| WARN cannot assign `x` in match guard | ||
| //~| WARN this error has been downgraded to a warning for backwards compatibility |
There was a problem hiding this comment.
as a next step we should make this a deny-by-default lint.
oli-obk
commented
Apr 23, 2019
That's fine. We do this all the time. I mean, every new syntactical feature is basically that.
There's also code for the exhaustiveness checks in match checking, we can't remove that. Let's merge this PR and then have a look at what effect killing the match borrow check duplication has (in a new PR) @bors r+ |
bors
commented
Apr 23, 2019
📌 Commit 87ef96d has been approved by |
bors
commented
Apr 23, 2019
bors
commented
Apr 23, 2019
☀️ Test successful - checks-travis, status-appveyor |
r? @oli-obk
Fix#60005. Follow up to #59903. Blocked on #53708, fixing the ICE in
src/test/ui/consts/match_ice.rs.