10.1.2. Base Code / Send and Sync. "Sync + Send"
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2.3k
- Forks
- 325
- PR merge metrics
- No merged PRs in 30d
Description
10.1.2. Base Code / Send and Sync. Fragment:
unsafe impl<T: Sync + Send> Send for Arc<T> {}
unsafe impl<T: Sync + Send> Sync for Arc<T> {}
It is unclear from the text of the book why the line about Send has the fragment Sync +:
unsafe impl<T: Sync + Send> Send for Arc {}
and why the line about Sync has a fragment + Send:
unsafe impl<T: Sync + Send> Sync for Arc {}
Would be nice to see in the book the clarification or details about that.
I also looked at (and it is still unclear)
Contributor guide
No contributing guide indexed for this repository
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 with the Nomicon’s “10.1.2. Base Code / Send and Sync” section and the linked Arc base discussion. Clarify why each unsafe impl requires both Sync and Send bounds, then update the book text so the relationship between the bounds and the implemented trait is explicit. Verify the documentation build and rendered example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100