You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MikeWalrus opened this issue
Aug 11, 2023
· 1 comment
· Fixed by #114749
Assignees
Labels
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsT-libsRelevant to the library team, which will review and decide on the PR/issue.
/// The sending-half of Rust's asynchronous [`channel`] type. This half can only be
/// owned by one thread, but it can be cloned to send to other threads.
///
/// Messages can be sent through this channel with [`send`].
Summary
Given that Sync is now implemented for Sender in #111087, the documentation for Sender should no longer mention that it's meant to be cloned. In my opinion, it's better to be consistent with the documentation for SyncSender, which has been Sync.
saethlin
added
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
and removed
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
labels
Aug 11, 2023
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsT-libsRelevant to the library team, which will review and decide on the PR/issue.
Location
rust/library/std/src/sync/mpsc/mod.rs
Lines 306 to 309 in a07bc13
Summary
Given that
Sync
is now implemented forSender
in #111087, the documentation forSender
should no longer mention that it's meant to be cloned. In my opinion, it's better to be consistent with the documentation forSyncSender
, which has beenSync
.rust/library/std/src/sync/mpsc/mod.rs
Lines 353 to 355 in a07bc13
The text was updated successfully, but these errors were encountered: