-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't emit cannot move errors twice in migrate mode #55221
Don't emit cannot move errors twice in migrate mode #55221
Conversation
☔ The latest upstream changes (presumably #55069) made this pull request unmergeable. Please resolve the merge conflicts. |
38b0425
to
b375728
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bors r+
if let Err(_place_err) = self.is_mutable(place, is_local_mutation_allowed) { | ||
if let (Err(_place_err), true) = ( | ||
self.is_mutable(place, is_local_mutation_allowed), | ||
self.errors_buffer.is_empty() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah great idea to let the ICE through if we have already signaled errors. Or at least I hope it’s a great idea.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(ugh I clearly misread the code 3 hours ago.)
@bors r+ |
📌 Commit b375728 has been approved by |
if let Err(_place_err) = self.is_mutable(place, is_local_mutation_allowed) { | ||
if let (Err(_place_err), true) = ( | ||
self.is_mutable(place, is_local_mutation_allowed), | ||
self.errors_buffer.is_empty() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just to be clear: this filter is going to affect more than just the migrate mode, right?
that is, I assume this will also cause us to stop emitting some move errors even in normal NLL mode?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or rather ... I guess it will stop us ... from ICE'ing in some scenarios under normal NLL mode if we've emitted an error already ...?
I don't know how I feel about that. I guess its fine.
Ugh sorry I had used my phone and I guess the review comment system there doesn't bubble out to here in a manner that bors can see! |
1 similar comment
Ugh sorry I had used my phone and I guess the review comment system there doesn't bubble out to here in a manner that bors can see! |
|
It looks like Bors might be stuck - all commits on the |
@bors r+ |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit b375728 has been approved by |
…te-messages, r=pnkfelix Don't emit cannot move errors twice in migrate mode Closes rust-lang#55154 cc rust-lang#53004 r? @pnkfelix
⌛ Testing commit b375728 with merge 7d04c95f0da7486f2a652fb7efd4e52fe01786ef... |
💔 Test failed - status-appveyor |
Needs to bless a file.
|
b375728
to
42a541e
Compare
@bors r=pnkfelix |
📌 Commit 42a541e has been approved by |
⌛ Testing commit 42a541e with merge 6e0a5b63d7e24d392bb2b9139bd9a4e61493da48... |
💔 Test failed - status-appveyor |
@bors retry 3 hour timeout |
☀️ Test successful - status-appveyor, status-travis |
Closes #55154
cc #53004
r? @pnkfelix