-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Fix unclear make_mut description #31397
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
Conversation
@bors: r+ rollup agreed, thanks! |
📌 Commit fa74a83 has been approved by |
/// Make a mutable reference into the given `Arc<T>` by cloning the inner | ||
/// data if the `Arc<T>` doesn't have one strong reference and no weak | ||
/// references. | ||
/// Make a mutable reference into the given `Arc<T>`. |
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.
make tidy
flagged the trailing space here
Changed the description of the `make_mut` copy-on-write behaviour in arc.rs The sentence "doesn't have one strong reference and no weak references." is a hard to understand double negative, which can be much more easily explained.
@steveklabnik My mistake for screwing up the whitespace. Can you re-approve for bors? |
@bors: r+ rollup no worries, I do it all the time :) |
📌 Commit 3cafce6 has been approved by |
The documentation for the `make_mut` function on `Arc<T>` contains a somewhat impenetrable double-negative that I was only able to fully grasp by looking at the implementation. Here's a quick rewrite that reads a lot better. The sentence "doesn't have one strong reference and no weak references." is a hard to understand, and it can be much more easily explained. In particular, such a double-negative could give English as a Second Language users even more trouble than native speakers. r? @steveklabnik
The documentation for the
make_mut
function onArc<T>
contains a somewhat impenetrable double-negative that I was only able to fully grasp by looking at the implementation. Here's a quick rewrite that reads a lot better.The sentence "doesn't have one strong reference and no weak references." is a
hard to understand, and it can be much more easily explained. In particular, such a double-negative
could give English as a Second Language users even more trouble than native speakers.
r? @steveklabnik