LinkedList::<T>::iter_mut() could return elements of type Pin<&mut T>
Open
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Assuming that the elements within a LinkedList never move in memory (which is normally the case), iterating over the list could return Pin<&T> or Pin<&mut T> rather than plain &T or &mut T.
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 issue’s LinkedList::::iter_mut() proposal and review the existing discussion in this RFC repository. Clarify the intended Pin<&T> and Pin<&mut T> API, its safety assumptions, and what decision or RFC outcome would count as done; no specific file or test is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100