Tracking Issue for `arc_raw_get_strong`
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-unimplemented
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(arc_raw_get_strong)]
This is a tracking issue for adding strong_count_from_raw to Arc and Rc for getting their strong count from a raw pointer.
Public API
impl<T: ?Sized, A: Allocator> Arc<T, A> {
pub unsafe fn strong_count_from_raw(ptr: *const T) -> usize {
...
}
}
impl<T: ?Sized, A: Allocator> Rc<T, A> {
pub unsafe fn strong_count_from_raw(ptr: *const T) -> usize {
...
}
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#792
- Implementation: #...
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed public API for Arc and Rc and the linked ACP, rust-lang/libs-team#792. The issue does not name implementation files or tests; completion requires the implementation, final comment period, and stabilization PR steps to be addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100