Skip to content

Improve message for rustc --explain E0507 #31270

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Feb 2, 2016
Merged

Conversation

ruuda
Copy link
Contributor

@ruuda ruuda commented Jan 28, 2016

E0507 can occur when you try to move out of a member of a mutably borrowed struct, in which case mem::replace can help. Mentioning that here hopefully saves future users a trip to Google.

E0507 can occur when you try to move out of a member of a mutably
borrowed struct, in which case `mem::replace` can help. Mentioning that
here hopefully saves future users a trip to Google.
@rust-highfive
Copy link
Contributor

r? @arielb1

(rust_highfive has picked a reviewer for you, use r? to override)

@arielb1
Copy link
Contributor

arielb1 commented Jan 31, 2016

r? @steveklabnik

@steveklabnik
Copy link
Member

Ha! Thank you.

@bors: r+ rollup

@bors
Copy link
Collaborator

bors commented Feb 1, 2016

📌 Commit f841f06 has been approved by steveklabnik

steveklabnik added a commit to steveklabnik/rust that referenced this pull request Feb 1, 2016
E0507 can occur when you try to move out of a member of a mutably borrowed struct, in which case `mem::replace` can help. Mentioning that here hopefully saves future users a trip to Google.
steveklabnik added a commit to steveklabnik/rust that referenced this pull request Feb 2, 2016
E0507 can occur when you try to move out of a member of a mutably borrowed struct, in which case `mem::replace` can help. Mentioning that here hopefully saves future users a trip to Google.
bors added a commit that referenced this pull request Feb 2, 2016
@bors bors merged commit f841f06 into rust-lang:master Feb 2, 2016
@ruuda ruuda deleted the improve-e0507 branch November 30, 2016 09:59
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants