-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Tracking issue for weak_ptr_eq #55981
Copy link
Copy link
Closed
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is a tracking issue for
rc::Weak::ptr_eqandsync::Weak::ptr_eq.Feature gate: #![feature(weak_ptr_eq)].
Steps:
Old issue:
Rchas a function calledptr_eqit compares if theRcpoints to the value, not the values themselves. I would like to add the same function toWeak. I got an implementation but have two questions:Weak::new(). I would argue always returnfalseif either one is dangling.