-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Implement RefCell::replace
and RefCell::swap
#43574
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @BurntSushi (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
src/libcore/cell.rs
Outdated
/// | ||
/// This function corresponds to [`std::mem::replace`](../mem/fn.replace.html). | ||
/// | ||
/// # Example |
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.
src/libcore/cell.rs
Outdated
/// | ||
/// This function corresponds to [`std::mem::swap`](../mem/fn.swap.html). | ||
/// | ||
/// # Example |
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.
s/Example/Examples
Those problems are fixed now. |
r? @sfackler |
/// | ||
/// # Panics | ||
/// | ||
/// This function will panic if the `RefCell` has any outstanding borrows, |
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.
"either RefCell
", right?
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.
There is only one RefCell
involved in a RefCell::replace
. This is different from RefCell::swap
, which does actually involve two of them.
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.
Oops, yeah, I thought this was below.
@@ -543,6 +543,59 @@ impl<T> RefCell<T> { | |||
debug_assert!(self.borrow.get() == UNUSED); | |||
unsafe { self.value.into_inner() } | |||
} | |||
|
|||
/// Replaces the wrapped value with a new one, returning the old value, |
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.
I wonder if the docs should mention that these are simply convenience functions for their one-liner implementations? I wouldn't want people thinking that they're more "magical" than they really are. Thoughts @steveklabnik? Not sure if we do something similar elsewhere.
ping @sfackler, looks like this is ready for your rereview! |
@bors r+ |
📌 Commit 846d373 has been approved by |
Implement `RefCell::replace` and `RefCell::swap` Tracking issue: #43570
☀️ Test successful - status-appveyor, status-travis |
Tracking issue: #43570